### Answer The deprecated API you're receiving notifications about is likely related to the conversation node tools deprecation scheduled for 04/18/2026 [(1) ]() . What's being deprecated: - The

tools

and

tool_ids

fields on conversation nodes with

type: "conversation"

What to check in your workflows: Look for conversation nodes that use tools. These need to be migrated to use

type: "subagent"

instead . How to identify affected nodes: - Check if you have any nodes with

type: "conversation"

that also have

tools

or

tool_ids

fields - These could be in your Conversation Flows or Conversation Flow Components Migration steps: For conversation nodes with tools, change

type

from

"conversation"

to

"subagent"

. If the node uses a

static_text

instruction, change it to

prompt

. All other fields remain the same . What happens on 04/18/2026: - Existing conversation nodes with tools will be automatically migrated to

type: "subagent"

- The API will stop accepting

tools

or

tool_ids

fields on

type: "conversation"

nodes If you're still unable to locate the deprecated API usage in your workflows, the deprecation might be occurring in API calls rather than in the dashboard UI. Check any custom code or integrations that interact with the Create/Update Conversation Flow APIs .

​ To learn more, see the sources I considered: [[1] Deprecating on 04/18/2026](https://docs.retellai.com/deprecation-notice/2026/04-18_conversation_node_tools) ​

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

@AI Evy how do i know which workspace is being flagged?

### Answer I don't have specific information in the available sources about how to identify which workspace is being flagged in the deprecation notification email. The email notification you received should ideally contain workspace-specific information, but the available documentation doesn't detail how workspace identification works in these deprecation notices. To identify the affected workspace, I recommend: Check out these potentially useful sources: - [Platform Changelogs | Retell AI]() - [Post Call Analysis Overview]() You may also want to: - Review the email notification itself for any workspace identifiers or organization details - Check if you have access to multiple workspaces and systematically review each one for the deprecated API usage - Contact Retell AI support directly for clarification on which specific workspace triggered the notification Would you like me to try to provide a general answer based on my knowledge instead?

message has been deleted

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

### Answer The notification is about the Phone Number API deprecation affecting specific fields. What's being deprecated: [(1) ]() [(2) ]() [(3) ]() The following fields are marked as deprecated in the Phone Number APIs: -

inbound_agent_id

-

outbound_agent_id

-

inbound_agent_version

-

outbound_agent_version

What to use instead: Replace the deprecated fields with these new array-based fields: -

inbound_agents

- array of agents with weights for inbound calls [(1) ]() -

outbound_agents

- array of agents with weights for outbound calls -

inbound_sms_agents

- array of agents with weights for inbound SMS -

outbound_sms_agents

- array of agents with weights for outbound SMS Where to check for usage: The deprecated fields appear in these Phone Number API endpoints: - Update Phone Number (

PATCH /update-phone-number/{phone_number}

) - List Phone Numbers (

GET /get-phone-number/{phone_number}

) [(2) ]() - Get Phone Number [(3) ]() To identify the affected code: Look for any API calls in your codebase that use

inbound_agent_id

,

outbound_agent_id

,

inbound_agent_version

, or

outbound_agent_version

when working with phone numbers. These are likely in your backend integration code rather than the dashboard UI. The new agent arrays support weighted routing - one agent is picked randomly for each call with probability proportional to the weight, and total weights must add up to 1 [(1) ]() [(2) ](

i.com/api-references/list-phone-numbers) [(3) ]() .

​ To learn more, see the sources I considered: [[1] Update Phone Number](https://docs.retellai.com/api-references/update-phone-number) [[2] List Phone Numbers](https://docs.retellai.com/api-references/list-phone-numbers) [[3] Get Phone Number](https://docs.retellai.com/api-references/get-phone-number) ​

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

### Answer No, the

create-phone-call

API is not affected by the Phone Number API deprecation [(1) ]() . The deprecation specifically targets the Phone Number APIs - Update Phone Number, List Phone Numbers, and Get Phone Number - which manage phone number configurations [(2) ]() . The deprecated fields are

inbound_agent_id

,

outbound_agent_id

,

inbound_agent_version

, and

outbound_agent_version

. The

create-phone-call

API uses different parameters:

from_number

,

to_number

,

override_agent_id

, and

override_agent_version

[(1) ]() . These fields are not being deprecated and will continue to work as expected . What you need to check: Look for any code that calls the Phone Number management endpoints (update, list, or get phone number details) , not the create-phone-call endpoint [(2) ]() .

​ To learn more, see the sources I considered: [[1] Create Phone Call](https://docs.retellai.com/api-references/create-phone-call) [[2] List Phone Numbers](https://docs.retellai.com/api-references/list-phone-numbers) ​

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

### Answer If you haven't directly used the Phone Number management APIs (List, Get, Update, or Import Phone Numbers) [(1) ]() [(2) ]() [(3) ]() , the deprecated fields might be getting used indirectly through: 1. Dashboard UI interactions When you configure phone numbers through the Retell dashboard, the UI may be calling these APIs in the background with the deprecated fields [(2) ]() [(3) ]() . 2. SDK usage If you're using the Retell SDK (like the JavaScript/TypeScript SDK) , check if you're calling phone number retrieval or update methods [(1) ]() [(3) ]() :

javascript
const phoneNumberResponse = await client.phoneNumber.retrieve('+14157774444') ;

[(3) ]() or

javascript
const phoneNumberResponses = await client.phoneNumber.list() ;

[(1) ]() 3. Import Phone Number API If you've imported custom telephony numbers, the Import Phone Number API also uses these deprecated fields (

inbound_agent_id

,

outbound_agent_id

,

inbound_agent_version

,

outbound_agent_version

) [(4) ]() . What to do: Since Retell's log analysis detected usage from your organization, the deprecated API calls are happening somewhere. Check: - Any automation tools or integrations that might be managing phone numbers - Third-party platforms that integrate with Retell - Any scripts that retrieve phone number configurations If you still can't locate the usage, contact Retell support directly at support@retellai.com with your organization ID to get specific details about where the deprecated API calls are originating.

​ To learn more, see the sources I considered: [[1] List Phone Numbers](https://docs.retellai.com/api-references/list-phone-numbers) [[2] Update Phone Number](https://docs.retellai.com/api-references/update-phone-number) [[3] Get Phone Number](https://docs.retellai.com/api-references/get-phone-number) [[4] Import Phone Number](https://docs.retellai.com/api-references/import-phone-number) ​

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