turbopuffer API
/v1/vectors endpoint removal
Deprecated, no dateSubscribe to turbopuffer APIShare
The turbopuffer API deprecated the /v1/vectors endpoint without a shutdown date. Calls made to /v1/vectors will eventually fail. turbopuffer API announced this change on December 1, 2024, noting that the endpoint is deprecated in favor of /v1/namespaces.
Calls it hits
/v1/vectors
What to use instead of these calls
Use /v1/namespaces instead.
In turbopuffer API's words
/v1/vectors deprecated in favor of /v1/namespaces
Facts
- API
- turbopuffer API
gcp-us-central1.turbopuffer.com - Kind
- Endpoint removal
- Announced
- December 1, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against turbopuffer API's own pages
Questions
When does this change take effect?
turbopuffer API deprecated /v1/vectors without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: turbopuffer 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 turbopuffer API 1
-
No date
/v1/vectors*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.