Uh oh!
There was an error while loading. Please reload this page.
docs(sessions): add POST /api/sessions/{sessionId}/chats/{chatId}/messages endpoint for persisting assistant messages - #215
Conversation
pradipthaadhi
commented
May 15, 2026
- Introduced a new POST endpoint to allow the upsertion of assistant chat messages into specified chats within a session.
- Detailed request and response schemas added, including validation rules for message structure and error handling.
- Updated navigation to include the new endpoint in the sessions documentation, enhancing the API's capabilities for chat management.
…sages endpoint for persisting assistant messages - Introduced a new POST endpoint to allow the upsertion of assistant chat messages into specified chats within a session. - Detailed request and response schemas added, including validation rules for message structure and error handling. - Updated navigation to include the new endpoint in the sessions documentation, enhancing the API's capabilities for chat management.
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…r clarity - Revised the description for `chatId` to specify its relationship with `sessionId`, enhancing user understanding of the API's chat management. - Clarified the message id conflict error description to explicitly state the nature of the conflict, improving the documentation's precision. - Updated the `id` field description to provide clearer guidance on its usage and generation, ensuring users have a better understanding of the chat id's context. - Adjusted the `parts` field description to simplify the schema definition, streamlining the documentation for better readability.