ACTION REQUIRED] [org_ZM6hm9TLOKq15OJJ] Deprecated API usage detected: Legacy list endpoints

Support Help
1

Hi there,

Action required: we detected continued usage of deprecated Retell API functionality in your account.

Unless you update your integration, affected requests may stop working when this deprecated functionality is removed.

Deprecation: Legacy list endpoints
Most recent use: Jun 8, 2026, 9:10 AM PDT
Affected workspace ID: org_ZM6hm9TLOKq15OJJ

Affected usage:

  • POST /v2/list-calls: 2263 use(s).

Migration details: Deprecating on 06/15/2026 - Retell AI

Please update your integration as soon as possible. Update the affected API requests according to the migration details above.

If you believe you are receiving this in error, contact Retell support and include the affected workspace ID above.

  • The Retell Team
2

Hello @carmines.digilabgrou Checking with the team on this. Best Regards

3

This is telling you that your app or AI agent is using an API endpoint that’s going away sometime soon… so you should migrate to v3/list-calls.

I can tell you the result from v2 and v3 of list-calls is not the same shape - so triple check the result from v3 before just flipping the one bit :slight_smile:

4

Hello @carmines.digilabgrou that notice is legitimate, and it’s specific to workspace org_ZM6hm9TLOKq15OJJ. It’s generated by an automated weekly check that counts API-key-authenticated traffic to the legacy POST /v2/list-calls endpoint, which is being removed on 2026-06-15. Dashboard activity is excluded (those sessions use a different auth path and already call v3), so the 2,263 hits are coming from a backend integration in that workspace — a script, scheduled job, low-code tool (Zapier/Make/n8n), or a service pinned to an older Retell SDK version.

To migrate before the cutover:

  • Endpoint swap: POST https://api.retellai.com/v2/list-calls → POST ``https://api.retellai.com/v3/list-calls.
  • Response shape changed (this is the most common silent regression): v2 returned a bare array; v3 returns { items, pagination_key, has_more } (and total if you pass include_total: true). Any loop currently treating the response as an array will break pagination — update it to read items and traverse with pagination_key + has_more.
  • Fastest fix if you use our official SDKs: upgrade the Python or TypeScript SDK to the latest version — client.call.list(...) already targets v3 there.
  • Migration doc: Deprecating on 06/15/2026 - Retell AI

If you’re not sure which integration is calling v2, the cleanest way to bisect is to rotate one API key at a time and watch next Monday’s notice — when the count drops to zero, that was the caller. The weekly notices will stop on their own once v2 traffic from the workspace ceases; no manual unsubscribe needed.

Thank You