recaps

Endpoints for creating and managing AI-powered channel recaps that summarize unread messages.

📄️Create a channel recap

Create a new AI-powered recap for the specified channels. The recap will summarize unread messages in the selected channels, extracting highlights and action items. This creates a background job that processes the recap asynchronously. The recap is created for the authenticated user.

📄️Get current user's recaps

Get a paginated list of recaps created by the authenticated user.

📄️Get recap limit status for the current user

Get the current user's recap usage limits and status, including daily usage, effective limits, and cooldown information.

📄️Mark all of the authenticated user's finished recaps as viewed

Mark every not-yet-viewed completed or failed recap belonging to the authenticated user as viewed at the current time. Pending and processing recaps are not affected. Returns the IDs of the recaps that were updated. The server broadcasts a `recap_updated` WebSocket event for each affected recap.

📄️Get a specific recap

Get a recap by its ID, including all channel summaries. Only the authenticated user who created the recap can retrieve it.

📄️Delete a recap

Delete a recap by its ID. Only the authenticated user who created the recap can delete it.

📄️Mark a recap as read

Mark a recap as read by the authenticated user. This updates the recap's read status and timestamp.

📄️Regenerate a recap

Regenerate a recap by its ID. This creates a new background job to regenerate the AI-powered recap with the latest messages from the specified channels.