Notion API
POST /v1/agents/{id}/chatStream endpoint removal
Deprecated, no dateSubscribe to Notion APIShare
Notion API deprecated POST /v1/agents/{id}/chatStream without giving a shutdown date yet.
Calls it hits
POST /v1/agents/{id}/chatStream
What to use instead of these calls
Call POST /v1/sessions with Accept: text/event-stream and parse server-sent events instead of NDJSON lines.
In Notion API's words
The alpha routes are deprecated If you use the alpha routes for listing agents, threads, messages, or chat, migrate to their replacements.
Facts
- API
- Notion API
api.notion.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Notion API's own pages
Questions
When does this change take effect?
Notion API deprecated POST /v1/agents/{id}/chatStream without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Notion API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Notion API 9
-
No date
PATCH /v1/blocks/{id}Parameter removal Deprecated, no date -
No date
PATCH /v1/data_sources/{id}Parameter removal Deprecated, no date -
No date
PATCH /v1/databases/{id}Parameter removal Deprecated, no date -
No date
PATCH /v1/pages/{id}Parameter removal Deprecated, no date -
No date
GET /v1/agentsEndpoint removal Deprecated, no date -
No date
PATCH /v1/agents/{id}/statusEndpoint removal Deprecated, no date -
No date
POST /v1/agents/{id}/chatEndpoint removal Deprecated, no date -
No date
/v1/agents/{id}/threads*Removal Deprecated, no date -
No date
/v1/threads/{id}/messages*Removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.