pipelines* endpoint removal

Deprecated, no dateSubscribe to LlamaCloud APIShare

LlamaCloud API has deprecated Index v1, including the /api/v1/pipelines* endpoints, without specifying a shutdown date. Calls directed to these pipeline endpoints will fail upon removal. This deprecation encompasses pipelines, data sources, and data sinks.

Calls it hits

/api/v1/pipelines*

What to use instead of these calls

Migrate to Index v2 by placing files into a directory via /api/v1/beta/directories, creating an index using /api/v1/indexes, and querying through POST /api/v1/retrieval/retrieve or /api/v1/chat. The transition requires more than updating endpoint identifiers, as Index v2 re-parses and re-embeds all files, consuming parse credits while dropping configurable chunking, configurable embedding, composite retrieval, and several connectors.

Index v2 parses and embeds every file again (parse credits) and drops configurable chunking and embedding, composite retrieval and several connectors.

In LlamaCloud API's words

Index v1 (pipelines, data sources, data sinks) is deprecated.

LlamaCloud API, Announcement

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: October 25, 2026
Verified: November 6, 2026, against LlamaCloud API's own pages

Questions

When does this change take effect?

LlamaCloud API deprecated /api/v1/pipelines* 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.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub