95622) . I don't have documentation specifying whether Retell AI's native HubSpot integration itself makes calls to these legacy endpoints or whether it will be updated automatically on your behalf. I'd recommend checking with Retell AI support directly for confirmation on how the HubSpot integration is affected. Visit [Documentation]() or [Hire certified Retell partner]() for further assistance.

### Answer The legacy list endpoints (including List Calls, List Chats, List Phone Numbers, List Retell LLMs, List Conversation Flows, List Conversation Flow Components, List Batch Tests, List Test Case Definitions, and List Test Runs) are deprecated as of 06/15/2026 and are no longer supported [(1) ]() [(2) ]() . To resolve this, migrate to the versioned endpoints: -

GET /list-batch-tests

->

GET /v2/list-batch-tests

-

GET /list-conversation-flow-components

->

GET /v2/list-conversation-flow-components

-

GET /list-conversation-flows

->

GET /v2/list-conversation-flows

-

GET /list-phone-numbers

->

GET /v2/list-phone-numbers

-

GET /list-retell-llms

->

GET /v2/list-retell-llms

-

GET /list-test-case-definitions

->

GET /v2/list-test-case-definitions

-

GET /list-test-runs/{test_case_batch_job_id}

->

GET /v2/list-test-runs/{test_case_batch_job_id}

-

POST /v2/list-calls

->

POST /v3/list-calls

-

GET /list-chat

->

POST /v3/list-chats

[(2) ]() Update your client calls to use the new method/path for each endpoint, and update your response handling to read

items

from the paginated response object instead of expecting a top-level array from the legacy endpoints. Continue using

pagination_key

and

has_more

for page traversal . On the HubSpot-specific side, the sources describe community discussion about a native GoHighLevel integration and a related deprecation warning question, but there's no documented explanation from Retell AI's official sources regarding how the native HubSpot integration specifically handles these legacy list endpoint calls [(3) ](

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

​ To learn more, see the sources I considered: [[1] Deprecation Overview](https://docs.retellai.com/deprecation-notice/overview) [[2] Legacy list endpoints removed for v2/v3 (06/15/2026)](https://docs.retellai.com/deprecation-notice/2026/06-15_legacy_list_endpoints) [[3] Discord message from @muhammad_03080 on 2026-07-01](https://discord.com/channels/1186424376300679209/1186462578310910112/1521774507591995622) ​

### Answer To resolve the deprecated legacy list endpoints, update each affected client call to its versioned replacement: -

GET /list-batch-tests

->

GET /v2/list-batch-tests

[(1) ]() -

GET /list-conversation-flow-components

->

GET /v2/list-conversation-flow-components

-

GET /list-conversation-flows

->

GET /v2/list-conversation-flows

-

GET /list-phone-numbers

->

GET /v2/list-phone-numbers

-

GET /list-retell-llms

->

GET /v2/list-retell-llms

-

GET /list-test-case-definitions

->

GET /v2/list-test-case-definitions

-

GET /list-test-runs/{test_case_batch_job_id}

->

GET /v2/list-test-runs/{test_case_batch_job_id}

-

POST /v2/list-calls

->

POST /v3/list-calls

-

GET /list-chat

->

POST /v3/list-chats

Steps: 1. Update each client call to the new method/path listed above . 2. Update response handling to read

items

from the paginated response object, instead of expecting a top-level array from the legacy endpoints . 3. Continue using

pagination_key

and

has_more

for page traversal . The versioned list endpoints return unified pagination fields:

items

,

pagination_key

, and

has_more

. I don't have documentation specifying how Retell AI's native HubSpot integration itself interacts with these legacy endpoints, or whether that integration will be updated automatically on your end. For confirmation on the HubSpot-specific behavior, visit [Documentation]() or [Hire certified Retell partner]() .

​ To learn more, see the sources I considered: [[1] Legacy list endpoints removed for v2/v3 (06/15/2026)](https://docs.retellai.com/deprecation-notice/2026/06-15_legacy_list_endpoints) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.