v0 API
POST /v1/mcp-servers/{id}/oauth/authorize endpoint removal
Deprecated, no dateSubscribe to v0 APIShare
v0 API has deprecated OAuth authorization for MCP servers without specifying a shutdown date. This removal affects calls made to the POST /v1/mcp-servers/{id}/oauth/authorize endpoint. Requests sent to this route now fail.
Calls it hits
POST /v1/mcp-servers/{id}/oauth/authorize
What to use instead of these calls
The documentation names no replacement, and the endpoint now answers 410 Gone.
In v0 API's words
OAuth authorization for MCP servers through the v0 API is deprecated.
Facts
- API
- v0 API
api.v0.dev - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against v0 API's own pages
Questions
When does this change take effect?
v0 API deprecated POST /v1/mcp-servers/{id}/oauth/authorize without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: v0 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 v0 API 1
-
No date
/v1/projects*Endpoint 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.