Retell AI API
GET /list-conversation-flow-components endpoint removal
Stopped workingSubscribe to Retell AI APIShare
On June 15, 2026, Retell AI stopped supporting the legacy GET /list-conversation-flow-components endpoint. Requests sent to this endpoint fail since that date.
Calls it hits
GET /list-conversation-flow-components
What to use instead of these calls
Call GET /v2/list-conversation-flow-components and read the results from items, paging with pagination_key while has_more is true.
In Retell AI API's words
After 06/15/2026, the legacy endpoints listed above will no longer be supported.
Facts
- API
- Retell AI API
api.retellai.com - Kind
- Endpoint removal
- Takes effect
- June 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Retell AI API's own pages
Questions
When does this change take effect?
Calls to GET /list-conversation-flow-components on Retell AI API stopped working on June 15, 2026.
What happens to calls after June 15, 2026?
They have failed since June 15, 2026.
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 Retell AI API 10
-
PATCH /update-agent/{id}Parameter removal Stopped working -
PATCH /update-chat-agent/{id}Parameter removal Stopped working -
POST /create-agentParameter removal Stopped working -
POST /create-chat-agentParameter removal Stopped working -
PATCH /update-agent/{id}Parameter removal Stopped working -
PATCH /update-chat-agent/{id}Parameter removal Stopped working -
POST /create-agentParameter removal Stopped working -
POST /create-chat-agentParameter removal Stopped working -
PATCH /update-agent/{id}Parameter removal Stopped working -
PATCH /update-chat-agent/{id}Parameter removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.