LlamaCloud API
/api/v1/data-sources* endpoint removal
Deprecated, no dateSubscribe to LlamaCloud APIShare
LlamaCloud API has deprecated /api/v1/data-sources* endpoints as part of Index v1 without announcing a shutdown date. Calls directed to these routes will eventually fail once the deprecation completes. This change affects all operations targeting data sources under the /api/v1/data-sources* path.
Calls it hits
/api/v1/data-sources*
What to use instead of these calls
Move each data source to an Index v2 directory at /api/v1/beta/directories, where SharePoint, Google Drive and S3 become connected folders. A migration decision is required for workloads using OneDrive, Box, Confluence, Jira or Azure Blob Storage, as Index v2 currently provides no connectors for them.
Index v2 has no OneDrive, Box, Confluence, Jira or Azure Blob Storage connector.
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-sources* 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-sinks*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.