LlamaCloud API
/api/v1/data-sinks* endpoint removal
Deprecated, no dateSubscribe to LlamaCloud APIShare
The /api/v1/data-sinks* endpoints are deprecated as part of the phase-out of Index v1, with no shutdown date announced. Calls to these routes will eventually fail once the deprecation completes. Developers using these endpoints should review their integrations to prepare for the transition away from Index v1.
Calls it hits
/api/v1/data-sinks*
What to use instead of these calls
Index v2 cannot attach a data sink directly, so writing to an external vector store becomes your own export job. To migrate, export an Index v2 output directory to the vector store with a custom exporter based on LlamaIndex's index-v2-data-sinks examples.
Index v2 cannot attach a data sink: writing to an external vector store becomes your own export job.
In LlamaCloud API's words
Index v1 (pipelines, data sources, data sinks) is deprecated.
Facts
- API
- LlamaCloud API
api.cloud.llamaindex.ai - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against LlamaCloud API's own pages
Questions
When does this change take effect?
LlamaCloud API deprecated /api/v1/data-sinks* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: LlamaCloud 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 LlamaCloud API 3
-
No date
/api/v1/data-sources*Endpoint removal Deprecated, no date -
No date
/api/v1/pipelines*Endpoint removal Deprecated, no date -
No date
/api/v1/sheets/*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.