# Subject: Re: \[IMMEDIATE ACTION REQUIRED\] Breaking Retell AI API change

**URL:** <https://community.retellai.com/t/subject-re-immediate-action-required-breaking-retell-ai-api-change/2197>\
**Category:** Support Help\
**Tags:** integrations\
**Created:** [April 1, 2026, 4:16pm UTC](https://community.retellai.com/t/subject-re-immediate-action-required-breaking-retell-ai-api-change/2197 "2026-04-01T16:16:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kindredluminous](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/kindredluminous/32/1391_2.png) [@kindredluminous](https://community.retellai.com/u/kindredluminous)\
**Post date:** [April 1, 2026, 4:16pm UTC](https://community.retellai.com/t/subject-re-immediate-action-required-breaking-retell-ai-api-change/2197/1 "2026-04-01T16:16:59Z")

</div>

Hi Retell Support,

I received your notice regarding the deprecated Phone Number API fields. I am currently using Retell for my AI receptionist service, integrated with [Make.com](http://Make.com) webhooks and Google Sheets for call logging.

To ensure our service doesn’t break, could you please clarify the following:

1. **Specific Fields** : Which specific fields in our current configuration are flagged as deprecated?
2. **Migration Guide** : Could you provide the specific documentation or migration guide for the new API version?
3. **Deadline** : What is the exact date when the old fields will stop functioning entirely?
4. **Webhook Impact** : Will this change affect webhook payloads, or only direct API calls?

We want to get this updated immediately to avoid any downtime.

Best regards,  
Kindredluminous

---

<div class="post-metadata">

**Author:** ![mark1](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/mark1/32/2524_2.png) [@mark1](https://community.retellai.com/u/mark1)\
**Post date:** [April 1, 2026, 4:28pm UTC](https://community.retellai.com/t/subject-re-immediate-action-required-breaking-retell-ai-api-change/2197/2 "2026-04-01T16:28:01Z")

</div>

Hi @kindredluminous

Here are the answers to your questions.

**Deprecated Fields:** The following single-agent fields are deprecated across Create/Import/Update/Get/List Phone Number APIs:

- **`inbound_agent_id`** , **`inbound_agent_version`**

- **`outbound_agent_id`** , **`outbound_agent_version`**

- **`inbound_sms_agent_id`** , **`inbound_sms_agent_version`**

- **`outbound_sms_agent_id`** , **`outbound_sms_agent_version`**

**Migration:** Replace them with weighted agent lists ( **`inbound_agents`** , **`outbound_agents`** , **`inbound_sms_agents`** , **`outbound_sms_agents`** ). For a single agent, use a list with one entry and **`weight: 1`**. Example:

```auto
{
  "inbound_agents": [
    { "agent_id": "yourAgentId", "agent_version": 3, "weight": 1 }
  ]
}

```

**Deadline:**  **March 31, 2026**. Existing data is auto-converted, but the old fields will no longer be supported after this date.

**Webhook Impact:** The deprecation notice specifically mentions the Phone Number **API endpoints** (Create, Import, Update, Get, List).However, if your [Make.com](http://Make.com) webhooks reference any of these deprecated fields when calling those APIs, you’ll need to update those calls.

Full details are on the ( [Deprecating on 03/31/2026 - Retell AI](https://docs.retellai.com/deprecation-notice/2026/03-31_phone_number_agent_fields) )

Thank You

---

<div class="post-metadata">

**Author:** ![kindredluminous](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/kindredluminous/32/1391_2.png) [@kindredluminous](https://community.retellai.com/u/kindredluminous)\
**Post date:** [April 1, 2026, 4:51pm UTC](https://community.retellai.com/t/subject-re-immediate-action-required-breaking-retell-ai-api-change/2197/3 "2026-04-01T16:51:46Z")

</div>

Thanks for the clarification. Our webhook-based integration is unaffected. We’ll use the new format if we need to update phone number configurations