v0 API
/v1/projects* endpoint removal
Deprecated, no dateSubscribe to v0 APIShare
The /v1/projects* endpoints are deprecated without a shutdown date. Calls to /v1/projects* will fail as projects are deprecated. Check your integrations if your code relies on these paths.
Calls it hits
/v1/projects*
What to use instead of these calls
Use chat metadata and vercelProjectId on chats, and the Vercel API for project operations.
In v0 API's words
v0 Projects are 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 /v1/projects* 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
POST /v1/mcp-servers/{id}/oauth/authorizeEndpoint 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.