Most necessary endpoints already exist, but some could be added for completeness and they should be documented as official APIs rather than internal APIs. Useful endpoints to add:
get action item list (e.g. integration with tracking tools or wallboards). Already possible by loading the full retro data but requires some filtering on the client side; could be good to offer a general items endpoint with a filter option
mark action item done via POST rather than WebSocket (again, integration with tracking tools). More generally, offering retro editing capabilities without websocket requirements
web hooks (registered & managed in settings for retro), called when retro state changes for any reason, but with delay and debouncing (maybe after 5 minutes of inactivity or after 1 hour of continuous activity)
And in the app, API key generation & management in settings (per retro)
Most necessary endpoints already exist, but some could be added for completeness and they should be documented as official APIs rather than internal APIs. Useful endpoints to add:
And in the app, API key generation & management in settings (per retro)