# Changelog (/reference/changelog.md)
  # Changelog [#changelog]

A chronological record of platform updates, new features, and important changes to Sent's APIs and services. For a summary of what changed between API versions, see [API v2 to v3 changes](/reference/api/v2-to-v3).

---

## 2026 [#2026]

### October 2026 [#october-2026]

#### Channels, 10DLC Campaigns, Contacts, and Webhooks [#channels-10dlc-campaigns-contacts-and-webhooks]

**Added: `channel.removed`.** When Sent removes a sender that had been approved, for example at your request, the webhook event is `channel.removed` with `INACTIVE`. It used to arrive as `channel.deactivated`, so a webhook subscribed to `channel.deactivated` alone no longer receives removals: add `channel.removed`, or subscribe to the `channel` parent. See [channel sub-types](/start/webhooks/event-types#channel-sub-types).

**Changed: a market holds up to 49 numbers.** On a US `TEN_DLC` market the limit is the campaign's and counts every number on it, including the one each Sender Profile sharing your organization's campaign receives. `LOCAL` markets have the same limit. A request over it is `400` on `numbers`. See [Managing Channels](/start/guides/managing-channels).

**Changed: a market with several numbers reports its healthiest one.** It is `ACTIVE` as soon as any of its numbers can send, and `sender_value` is a live number. Each entry in `numbers` carries its own status.

**Changed: a campaign's volume tier is fixed once it is submitted to TCR.** An update that moves `volume` across `2000` after submission is refused with `409 CONFLICT_017`. Changing `volume` no longer moves money on its own. See [Update or delete a campaign](/start/advanced/10dlc-campaigns-api#update-or-delete-a-campaign).

**Changed: contact search matches any phone format.** `search` on `GET /v3/contacts` compares digits, so `+12025550123`, `202-555-0123`, and `(202) 555 0123` find the same contact, and part of a number matches too.

**Changed: a suspended Sender Profile can't be changed.** A request that changes or deletes it is refused with `403 BUSINESS_014`, even with your organization's key, and the message names the suspended account.

**Changed: webhook signing secrets in the dashboard.** The dashboard shows a webhook's signing secret once, when you create the webhook or rotate its secret. See [Getting Started with webhooks](/start/webhooks/getting-started).

#### MMS: Shared Template Bodies and an Attachment Required [#mms-shared-template-bodies-and-an-attachment-required]

**Changed: MMS falls back to the shared template body.** MMS text now comes from the template's `mms` body, then its `multiChannel` body, then its `sms` body, as RCS does. A template with a shared or SMS body lists `mms` among its channels. The subject and template media still come only from an `mms` body. See [Template Definition](/reference/api/template-definition#mms-body-content-object).

**Changed: a send pinned to MMS needs an attachment.** `channel: ["mms"]` with no `media_urls` and no media in the template's `mms` body is refused with `400` (`VALIDATION_001`) instead of going out as a text-only MMS. Send text-only messages on `sms`.

**Changed: Meta's approval covers MMS.** When Meta approves a template, its MMS channel is approved with SMS and RCS, rather than waiting for a separate Sent review.

#### Voice: Numbers Work Without a Callback URL [#voice-numbers-work-without-a-callback-url]

**Changed: a voice number without a callback URL is `ACTIVE`.** It can be your default line like any other. Calls placed from your app on it connect straight to the phone number, app user, or room they dial. Calls to the number are still declined with `callback_not_configured`. See [Change a voice number](/start/guides/managing-channels#change-a-voice-number).

**Changed: setting `callback_url` no longer changes status.** `PATCH /v3/channels/voice/{number}` with a `callback_url` replaces the URL and keeps the number's status and signing secret.

#### Webhooks: Version 2 [#webhooks-version-2]

**Added: version 2 webhooks, the new default.** Webhooks you create are signed with the [Standard Webhooks](https://www.standardwebhooks.com) headers `webhook-id`, `webhook-timestamp`, and `webhook-signature`, with the same `whsec_` signing scheme and JSON body. Send `"webhook_version": 1` on `POST /v3/webhooks` to keep the older delivery. Existing webhooks stay on version 1 and are unchanged. Every webhook response carries `webhook_version`. See [Webhook Versions](/start/webhooks/event-types#webhook-versions).

**Added: `is_inheritable` on version 2 webhooks.** Your organization's inheritable webhook receives every Sender Profile's events, and each profile sees it but can't change it (`409 CONFLICT_016`). `sender_profile` clones remain on version 1. See [Inheritable webhooks](/start/webhooks/event-types#inheritable-webhooks-version-2).

**Changed for version 2:**

- Failed deliveries are retried automatically with increasing delays, so `retry_count` and `timeout_seconds` apply to version 1 only.
- Rotating the secret signs deliveries with both the old and new secret for 24 hours.
- A test is queued for delivery, and the response says it was queued rather than delivered.

#### Voice Client: `@sentdm/voice-client` Replaces `@sentdm/voice` [#voice-client-sentdmvoice-client-replaces-sentdmvoice]

**Changed: the browser SDK is `@sentdm/voice-client`.** `@sentdm/voice` is deprecated on npm and stays installable. [`@sentdm/voice-client`](https://www.npmjs.com/package/@sentdm/voice-client) 0.2.0 has the same client, calls, events, and errors, and the React provider and hooks moved from `@sentdm/voice/react` to [`@sentdm/voice-client-react`](https://www.npmjs.com/package/@sentdm/voice-client-react). See [Migrate From `@sentdm/voice`](/sdks/voice#migrate-from-sentdmvoice).

**Changed: the SDK exchanges the voice token itself.** `tokenProvider` must return the `token` from `POST /v3/voice/tokens` unchanged. The SDK exchanges it with Sent on every register and refresh, so nothing from the calling engine passes through your backend or your app. A token Sent refuses fails `register()` with `TokenInvalidError`.

**Changed: `baseURL` replaces `telemetry.baseURL`.** The option sets the Sent API origin the token exchange and telemetry use, `https://api.sent.dm` by default. `telemetry` keeps `disabled`.

**Changed: the calling engine ships inside the SDK.** It loads on the first `register()`, and your app installs no package for it.

#### Voice: Agents Answer Calls (Preview) [#voice-agents-answer-calls-preview]

**Added: voice agents.** `POST /v3/voice/agents` creates an agent of yours that answers calls to your numbers over a WebSocket, in text or in audio, with the tools, transfer targets, fallback, and limits you give it. `GET`, `PATCH` and `DELETE /v3/voice/agents/{id}` read, change and remove it, and `POST /v3/voice/agents/{id}/rotate-secret` rotates the secret Sent signs its handshake with. See [Voice agents](/start/guides/voice-agents).

- **`GET /v3/voice/voices`** lists the voices and languages a text agent's `speech` accepts.
- **`agent_id` on `POST` and `PATCH /v3/channels/voice`** binds a number to an agent, and `routes_to` on every voice number says who answers it. Calls follow a binding within about an hour.
- **The connect flow and the protocol are in Preview**, version 0.2.0 of `sent.voice.v1`. See [Connect a voice agent](/start/guides/voice-agent-connect) and the [voice agent protocol](/reference/api/voice-agent-protocol).

**Added: `mode` and `agent_id` on calls.** Every `call.*` event and every call record carry `mode`, `inapp` or `agent`, and an agent call carries `agent_id`. `GET /v3/voice/calls` filters on both. A `call.agent_connected` event is sent once the agent's session starts. See [Call events](/start/webhooks/event-types#call).

**Added: `connected_number`, `caller_id_used` and `legs` on the call record.** `GET /v3/voice/calls` and `GET /v3/voice/calls/{id}` say which number a forwarded or fallback call was connected to, which caller id the dialled leg showed, and the legs the call was billed for, each with its `direction`, `number`, `billed_minutes`, `cost` and `currency`. A forwarded or fallback call is one record with two billed legs. See [The Call Record](/start/guides/managing-calls#the-call-record).

**Added: `CONFLICT_014` and `CONFLICT_015`.** Deleting an agent a number routes to, or another agent transfers to, is `409` `CONFLICT_014`. Hanging up or recording a call an agent answers through the API is `409` `CONFLICT_015`. `call.failed` gains `agent_busy` and `agent_unreachable`. See the [Error Catalog](/reference/api/error-catalog).

#### Voice: Calls and Tokens Move Under `/v3/voice` [#voice-calls-and-tokens-move-under-v3voice]

**Changed: the voice API lives under `/v3/voice`.** Calls moved from `/v3/calls` to `/v3/voice/calls`, with the same requests and responses, and voice tokens from `POST /v3/channels/voice/tokens` to `POST /v3/voice/tokens`. The old paths are removed, without aliases. Voice numbers stay at `/v3/channels/voice` with the other channels. See [Calls, Recordings, and Participants](/start/guides/managing-calls) and [Calls From Your App](/start/guides/in-app-calls).

**Added: `mode` on every call.** Call records carry `mode`, which is `inapp` on every call.

**Changed: voice tokens are opaque.** `POST /v3/voice/tokens` returns a token prefixed `vt_`, signed by Sent. Treat it as opaque and hand it to the voice client SDK unchanged.

#### WhatsApp: Disconnect, Multi-Line Free Text, and Fixes [#whatsapp-disconnect-multi-line-free-text-and-fixes]

**Added: disconnect a WhatsApp Business Account.** Channels > WhatsApp has a **Disconnect** button next to **Switch Account**, for organizations and Sender Profiles. See [Disconnect a WhatsApp Business Account](/start/guides/connect-whatsapp#disconnect-a-whatsapp-business-account).

- **WhatsApp falls back to SMS** after a disconnect, until you connect an account again.
- **A number provided by Sent has to be deregistered and deleted in WhatsApp Manager first**, because Meta offers no way to remove it for you. Until then the disconnect is refused and nothing changes. Once it is off the account, the number is released, unless it is also your SMS number.
- **Accounts sharing the same WhatsApp Business Account keep working** when you disconnect yours.

**Changed: free-form `text` keeps line breaks, tabs, and runs of spaces** on every channel. These were rejected with `400` before, so multi-line messages and WhatsApp list and quote formatting could not be sent. Template variable values are still refused if they contain a line break, a tab, or more than four consecutive spaces. See [Sending free-form text](/start/guides/sending-messages#sending-free-form-text-without-a-template).

**Changed: a matching area code adds to match specificity.** It used to break ties only between routes that ranked equal. A route on a number in the recipient's area code now ranks ahead of one that matches as specifically without it, and numbers you held before October 9 now carry their area code too. See [Choosing the sending number](/reference/channel-routing#choosing-the-sending-number).

**Changed: your US SMS number is pre-verified for WhatsApp.** Once it is on your campaign, Sent pre-verifies it with Meta and WhatsApp signup offers it first, with no verification code to enter.

**Fixed:**

- WhatsApp STOP, HELP, and START auto-replies go out even when the contact's previous message is older than 24 hours.
- Meta-provided +1 555 numbers are accepted as WhatsApp senders in `channels.whatsapp` on `POST /v3/messages`. They are still refused for SMS, MMS, and RCS.
- Template word counts match Meta's: a symbol standing alone, such as a `|` between two variables, counts as a word. See [Template Definition](/reference/api/template-definition).
- WhatsApp sends are no longer blocked because your business is not yet verified with Meta. An account is treated as healthy whenever Meta reports it can send messages.

#### Webhooks: WhatsApp Number Events on `channel` [#webhooks-whatsapp-number-events-on-channel]

**Added: WhatsApp milestones on the `channel` family**, with `payload.channel` set to `whatsapp`. See [WhatsApp channel events](/start/webhooks/event-types#whatsapp-channel-events).

- **`channel.submitted`** when you claim a number Sent supplied that can't send yet.
- **`channel.activated`** when the number is registered, or when Meta approves its display name.
- **`channel.changes_requested`** when Meta rejects the display name, with Meta's reason in `payload.reason` when it gave one.
- **`channel.deactivated`** when the number is deregistered and returned to Sent.

#### Messages: Choose the Sending Number [#messages-choose-the-sending-number]

**Added: `channels` on `POST /v3/messages`.** `channels.sms` lists which of your SMS numbers a send may go out from, as a list of entries with a `from` each, for example `{"sms": [{"from": ["+12125550000", "+14155550000"]}]}`. See [Send from specific numbers](/start/guides/sending-messages#send-from-specific-numbers).

- **It combines with `channel`.** `"channel": ["sms"]` with an `sms` list sends on SMS from those numbers.
- **Routes pinned to a number you did not list are removed**, and routing picks among the rest as usual. The numbers from every entry apply to every recipient.
- **`country` and `strategy` are optional** on each entry. Both are stored with the message but do not change routing yet.
- **A malformed `channels` answers `400`**: a key that is not a channel (including `sent`), the same channel twice, an empty list, an entry with an empty `from`, or an entry that is not E.164.
- **The numbers are checked per message, at send time.** The request is accepted with `202`, and a message that lists a number that is not an active SMS sender on your account ends `BLOCKED` with `BUSINESS_029`. The `reason` names the number by its position, for example `channels.sms[0].from[1]`.
- **The choice stays with the message** through a scheduled or quiet-hours release, a resend, and a reroute after a delivery failure.

**Changed: area code breaks ties between your SMS numbers.** When several of your SMS routes rank equal for a recipient, the one whose number has the same area code as the recipient wins. This applies whether or not the send lists numbers. It never removes a route: every number still reaches every recipient its route covers. See [Choosing the sending number](/reference/channel-routing#choosing-the-sending-number).

**Added: error code `BUSINESS_029`.** A number listed in `channels` is not an active sender on your account. See the [Error Catalog](/reference/api/error-catalog#business_029-requested-sender-is-not-available-on-this-account).

#### Authentication: API Key as a Bearer Token [#authentication-api-key-as-a-bearer-token]

**Added: `Authorization: Bearer` on the v3 API.** Every v3 endpoint accepts your API key as `Authorization: Bearer <api key>`, as an alternative to the `x-api-key` header, for clients that can only send OAuth2 or Bearer credentials. See [Authentication](/reference/api/authentication).

- **It is the same key.** There is no separate token to create.
- **Send one header or the other.** If a request carries both, the API uses `x-api-key` and ignores `Authorization`.
- **The `Bearer` scheme name is case-insensitive.** Any other scheme, such as `Basic`, counts as a missing key.

#### Voice: Phone Calls, Voice Tokens, and Call Webhooks [#voice-phone-calls-voice-tokens-and-call-webhooks]

Phone calls on the numbers you hold, driven by your own callback URL; a browser SDK for calls from your app; and a `call` webhook family.

**Added: voice numbers.** `POST /v3/channels/voice` turns calls on for a number you hold, or gives you a new US number, with the `callback_url` Sent asks what to do with each call and the `callback_secret` the questions are signed with. Read them with `GET /v3/channels/voice`, change one with `PATCH /v3/channels/voice/{number}`, rotate the secret with `POST /v3/channels/voice/{number}/rotate-secret`, and check the URL with `POST /v3/channels/voice/{number}/test` before the first call. `GET /v3/channels` lists them under `voice`. See [Voice](/start/guides/managing-channels#voice).

**Added: the callback contract.** When a call arrives or a caller presses a key, Sent POSTs a signed `call.request` or `call.input` question and follows your answer: `connectToUser`, `connectToNumber`, `connectToConference`, `playMenu`, `park`, `hangup` or `reject`, after any `say`, `play`, `sendDigits`, `startRecording`, `stopRecording`, `answer` and `setCookie` instructions. Version `1`, camelCase. See [Answering Calls](/start/guides/answering-calls) and the [Voice Callback Contract](/reference/api/voice-callback).

**Added: calls.** Every call is a record under `/v3/voice/calls`: list and read calls, hang one up, start or stop a recording, list recordings, and add, mute, or remove conference participants. See [Calls, Recordings, and Participants](/start/guides/managing-calls).

**Added: voice tokens and `@sentdm/voice`.** `POST /v3/voice/tokens` mints a short-lived token for a user of your app, and the [`@sentdm/voice`](https://www.npmjs.com/package/@sentdm/voice) browser SDK places and receives calls with it. See [Calls From Your App](/start/guides/in-app-calls) and the [Voice SDK](/sdks/voice).

**Added: `call` webhooks.** `call.initiated`, `call.answered`, `call.completed` with `duration_seconds` and `price`, `call.failed` with `reason`, and `call.recording_ready` with `recording_id`. Subscribe to `call`. Payloads are snake_case like every other family; the callback contract is camelCase. See [Call events](/start/webhooks/event-types#call).

**Added: error codes.** `VALIDATION_011`, `RESOURCE_015`, `RESOURCE_017`, `BUSINESS_011` for calls, `BUSINESS_022` to `BUSINESS_028`, `CONFLICT_007` to `CONFLICT_009` and `CONFLICT_011`, plus the call failure reasons. See the [Error Catalog](/reference/api/error-catalog#call-failure-reasons).

**Added: voice in the server SDKs.** Every SDK exposes the voice endpoints as the `calls`, `calls.participants` and `channels.voice` resources: [`@sentdm/sentdm`](https://www.npmjs.com/package/@sentdm/sentdm) 0.42.0, [`sentdm`](https://pypi.org/project/sentdm/) 0.42.0 for Python, [Go](https://github.com/sentdm/sent-dm-go/releases/tag/v0.39.0) 0.39.0, [Java](https://github.com/sentdm/sent-dm-java/releases/tag/v0.41.0) 0.41.0, [C#](https://www.nuget.org/packages/Sentdm/0.38.0) 0.38.0, [PHP](https://github.com/sentdm/sent-dm-php/releases/tag/v0.36.0) 0.36.0 and [Ruby](https://rubygems.org/gems/sentdm/versions/0.35.0) 0.35.0. See [SDKs](/sdks).

#### Messages: Cancel a Scheduled Send [#messages-cancel-a-scheduled-send]

**Added: `POST /v3/messages/{id}/cancel`.** Call off a message you scheduled with `scheduled_at`, before it is released for sending. The message moves to the new terminal status `CANCELLED` and is never sent. See [Cancelling scheduled messages](/start/guides/cancelling-messages).

- **Only a `SCHEDULED` message can be cancelled.** A message that has already been released, is in flight, or has finished answers **409** with `BUSINESS_006`. The release sweeper runs every 30 seconds, so a cancellation sent within about a minute of the scheduled instant can lose that race.
- **One message per call.** A send to several recipients, or on several channels, is one message per recipient per channel, each with its own id. There is no bulk form.
- **Cancelling is free**, and nothing had been charged: a scheduled message is priced at release. A cancelled message is excluded from your deliverability rate.
- **The 200 body is the message**, in the same shape `GET /v3/messages/{id}` returns, plus `scheduled_at`. `events` is the timeline as it stood just before the cancellation; the `CANCELLED` activity entry lands a moment later.
- **Repeating a cancellation answers 200**, with the same body, and publishes no second event.
- `404` for an unknown id, `400` for an id that is not a UUID.

**Added: the `message.cancelled` webhook sub-type.** It fires exactly once per cancellation and carries `scheduled_at`, the release instant that was called off, so a consumer that recorded a future send from `message.scheduled` can un-record it. `body` is `null`, and it carries no `schedule_reason` and no `reason_code`.

- **Action required** if you subscribe with `event_filters`: add `cancelled` to the `message` list to receive it. A subscription to the `message` parent receives it with no change.

**Changed: `CANCELLED` joins the message status values.** `GET /v3/messages/{id}` reports it, and keeps reporting the message's `scheduled_at` afterwards, as does `GET /v3/messages/{id}/activities`. A handler that switches on `message_status` should treat it as terminal.

#### Sender Profiles: Opt-In Inheritance and a New Billing Default [#sender-profiles-opt-in-inheritance-and-a-new-billing-default]

**Breaking: inheriting the organization's US 10DLC brand and campaign is opt-in.** `POST /v3/sender-profiles` used to give a profile created without `compliance` the organization's brand and campaign, so its `TEN_DLC` markets ran on the organization's registration. It now has neither, and inherits only where `compliance` says `{ "inherit": true }`. See [Dedicated, inherited, or absent](/start/advanced/sender-profiles-api#dedicated-inherited-or-absent).

- **Action required** if you create profiles without `compliance` and expect their `TEN_DLC` markets to run on your registration: send `"compliance": { "brand": { "inherit": true }, "campaign": { "inherit": true } }`.
- `"brand": { "inherit": true }` on its own inherits the brand only. The campaign is then the profile's own.
- Inheriting the campaign while the brand is the profile's own, or `{ "inherit": false }`, is a **400** on `compliance.campaign`.
- Inheriting a brand or campaign your organization doesn't have is a **400** on a `TEN_DLC` market, naming the field. It used to leave the profile waiting in `PROVISIONING`.
- On a `TEN_DLC` market, an empty `compliance.brand` or `{ "inherit": false }` on its own is a **400**: it names no identity to file against.
- `POST /v3/channels/sms` can now move a profile that owns and inherits nothing onto your organization's registration, with the same `{ "inherit": true }`.

**Changed: omitting `billing` bills the profile first, with your organization covering the rest.** A profile created without `billing` used to pay alone. It now pays from its own balance, and your organization's balance covers what the profile's can't. `{ "inherit": false }` bills the profile alone, and `{ "inherit": true }` bills your organization. See [Billing](/start/advanced/sender-profiles-api#billing).

- Existing profiles with no billing arrangement were moved to the new default, so your organization's balance can now cover their shortfalls.
- Reads report the default as `{ "inherit": false }`. `settings.billing_model` on `GET /v3/account` reports `profile_and_organization` for it.

**Added: `502` on `POST /v3/sender-profiles`** when Meta can't be reached to verify `channels.whatsapp`. Nothing is created, so the request can be sent again.

**Added: an email when an SMS sender goes live.** "Your SMS sender for \{Country\} is now active" goes to the recipients the profile's `notifications` setting names, alongside the existing emails for a removed or declined sender.

#### Fixes [#fixes]

**Fixed: SMS delivery reports no longer move a message back to `QUEUED`.** On some SMS routes, a late report could move a `SENT` message back to `QUEUED` and fire a stray `message.queued` webhook. A message whose receipt never arrives now ends as `DELIVERED` when the carrier's report window closes, and a carrier report of a cancelled or deleted message ends as `FAILED`.

**Fixed: template webhooks reach every account holding the template.** When Meta changes a WhatsApp template's status, category, or quality, Sent now applies it to every account that holds that template, an organization and its Sender Profiles alike, and fires `template.*` webhooks for each. Only one of them used to receive it.

### September 2026 [#september-2026]

#### SMS Markets: Clear `ACTION_NEEDED` With One Call [#sms-markets-clear-action_needed-with-one-call]

`PATCH /v3/channels/sms/{country}/{type}` now supplies whatever a market is waiting on, in every market you hold, not only US `TEN_DLC`. See [Correct what it holds](/start/guides/managing-channels#correct-what-it-holds).

**Added: documents on the market `PATCH`.** Send `multipart/form-data` with each file in a part named after the document's key. `compliance` and `numbers` can ride in the same form as text parts holding their JSON.

- A file that matches no document the market asks for is a **400** listing the expected keys. A file the upload rules refuse is a **422**.
- `compliance` still applies only to a market that registers with a regime. Anywhere else it's a **400**.

**Added: `numbers` on the market `PATCH`.** It takes the same list as `POST /v3/channels/sms` and replaces what a `LOCAL` or `TEN_DLC` market asks for.

- A `LOCAL` market claims the new numbers from inventory straight away. A `TEN_DLC` market assigns them once its campaign is approved, and needs a campaign of the profile's own.
- A list that leaves out a number already assigned is a **400**. The call never releases a number.

**Changed: a registration sent back for correction is fixed with the same `PATCH`.** A filed identity used to be a **409** even when Sent had asked you to correct it. When the market reports `ACTION_NEEDED` for a correction, `compliance.brand` is now accepted, and the correction sends the registration back to Sent for review. A filed identity with no correction asked for is still a **409**.

**Changed: `reason` names where to send what's owed.** An `ACTION_NEEDED` market's `reason` now points to its `PATCH`. That holds for documents and corrections too.

#### Channels: `channel.rejected`, Corrected Event Timing, and Stricter SMS Market Validation [#channels-channelrejected-corrected-event-timing-and-stricter-sms-market-validation]

One new `channel` sub-type, three timing fixes, and two validation changes to `POST /v3/channels/sms`, one of them breaking.

**Breaking: a market that pre-registers its sender must be sent with its documents.** `POST /v3/channels/sms` for a market whose requirements include a document now answers **422** when that document isn't attached or an uploaded file is rejected, naming each missing key under `compliance`. It previously answered `201` or `202` and left a market waiting on a file the call had promised to collect. The market isn't added, so nothing needs cleaning up.

- **Action required** if you add such markets with a JSON body: send the request as `multipart/form-data`, with each document as a part named after its requirement key. See [Add the market](/start/guides/managing-channels#add-the-market).

**Changed: `sender_value` is required for `ALPHANUMERIC`.** `POST /v3/channels/sms` and `POST /v3/sender-profiles` answer **400** when `number_type` is `ALPHANUMERIC` and `sender_value` is missing or blank. An alphanumeric sender is one you choose, so there is nothing to provision without it.

**Added: `channel.rejected`.** A market's sender that is turned down before it ever went live now has its own sub-type: The Campaign Registry rejecting its campaign, or a sender still being set up being withdrawn. `payload.reason` carries the explanation when one was given. Both used to be indistinguishable from `channel.deactivated`, which means a sender that worked stopped. Subscribe to `channel` or add the `rejected` filter to receive it. See [Channel sub-types](/start/webhooks/event-types#channel-sub-types).

**Channel events: corrected timing.**

- **Changed**: `channel.approved` for a 10DLC market fires when the carriers elect your campaign. It previously fired when the campaign was shared with an upstream connectivity partner, days before a verdict existed.
- **Fixed**: Submitting a brand or campaign to The Campaign Registry now reports `channel.submitted`. It previously reported nothing.
- **Fixed**: Requesting a sender for a market that registers with nobody reports `channel.activated` once, not twice.
- **Fixed**: A market that pre-registers its sender no longer reports a `channel.deactivated` it never earned on the way to going live.

#### Messages and Channels: Reason Codes for Every Non-Success Status [#messages-and-channels-reason-codes-for-every-non-success-status]

A message that doesn't go out, and a channel that can't send, now say why.

**Added: `reason_code` and `reason` on messages.** `message.failed`, `message.filtered` and `message.blocked` webhooks, `GET /v3/messages/{id}` (top level and on each event) and `GET /v3/messages/{id}/activities` carry both. They're omitted on every successful status. See [Message Outcome Codes](/reference/api/error-catalog#message-outcome-codes).

- `reason_code` is a stable code to branch on. `reason` is a sentence to show a person, and its wording may improve.
- A cause the API already rejects synchronously keeps its code: an opted-out recipient is `BUSINESS_004`, a low balance `BUSINESS_003`, an invalid number `VALIDATION_002`.
- Outcomes only a message can have are `DELIVERY_001` to `DELIVERY_016`. The codes are Sent's classification and never a carrier's own code.
- New `BUSINESS_017` to `BUSINESS_020`, including `BUSINESS_020` for the onboarding-stage message limit.
- v2 is unchanged.

**Added: `reason_code` on channels.** Every SMS market, WhatsApp account and RCS agent that isn't `ACTIVE` carries `reason_code` (`CHANNEL_001` to `CHANNEL_011`) and `reason`, on `GET /v3/channels`, the single-market reads and Sender Profiles, and on `channel.*` webhooks for SMS markets. See [Channel Status Reasons](/reference/api/error-catalog#channel-status-reasons).

**Changed: `note` is replaced by `reason`.** SMS market responses no longer return `note`. The same sentence is now `reason`. **Action required** if you read `note`: read `reason`, and branch on `reason_code`.

**Changed: WhatsApp reports `ACTION_NEEDED` when it's waiting on you.** A WhatsApp channel with no business account connected (`CHANNEL_006`) or no phone number (`CHANNEL_007`) used to report `PROVISIONING`.

#### SMS: US Territories Reached From a US Number [#sms-us-territories-reached-from-a-us-number]

A US `TEN_DLC` or `LOCAL` number now also sends to Puerto Rico, the US Virgin Islands, Guam, American Samoa, the Northern Mariana Islands and the US Minor Outlying Islands. Existing numbers were given the routes, so no action is needed. See [Channel Routing](/reference/channel-routing#how-auto-detect-resolves-a-channel).

- Where a territory accepts alphanumeric senders, Sent sets one up on your first send there and tries it before your number.
- A failed delivery now reroutes when the carrier refused the sender itself or no route reached the destination network. Each reroute is charged as a send.

#### MMS: Inbound Attachments on `message.received` [#mms-inbound-attachments-on-messagereceived]

An inbound MMS now carries a `media` array: each attachment's `url`, and its `mime_type`, `size_bytes` and `hash_sha256` when the carrier declared them. The `url` is the carrier's own link, which needs no authentication and expires on the carrier's schedule, so download the file on receipt. `media` is omitted when there are no attachments. See [Inbound MMS](/start/guides/mms#inbound-mms).

#### Webhooks: Delivery Fixes [#webhooks-delivery-fixes]

- **Rotated secrets apply to queued events.** Each delivery is signed with the webhook's current secret, URL and timeout when it's sent. An event queued before a rotation used to arrive signed with the old secret and fail.
- **Repeated test sends are delivered.** Every test uses fresh sample ids. A second test of the same event used to be reported as failed without being sent.
- **Test sends don't count toward auto-disable.** A failed test no longer moves the webhook toward being switched off.
- **Your organization's event history includes its clones'.** `GET /v3/webhooks/{id}/events` on your organization's webhook also lists the events its Sender Profile clones delivered.

#### Webhooks: Sender Profile Clones [#webhooks-sender-profile-clones]

Your organization's webhook can be cloned onto every Sender Profile, so every profile's events reach your endpoint.

**Added: `sender_profile` on webhooks.** `POST /v3/webhooks` and `PUT /v3/webhooks/{id}` accept `sender_profile`, with its own `event_types` and `event_filters`. When it selects any event, Sent clones the webhook onto every Sender Profile under your organization, including profiles you create later. Each clone is a webhook the profile owns, with your webhook's URL and signing secret, and receives the profile's events that `sender_profile` selects. See [Sender Profile Events](/start/webhooks/event-types#sender-profile-events).

- Your changes to the webhook update every clone, including one a profile edited. A clone a profile deleted stays deleted.
- An event a clone delivers names the profile in `payload.account_id`.
- Webhook responses don't include `sender_profile`. It's a request field on create and update only.
- On an update, omitting `sender_profile` keeps the clones' events. Send `"sender_profile": {"event_types": []}` to delete the clones.
- `event_types` can be empty when `sender_profile.event_types` isn't, so a webhook can feed its clones alone.
- A request made as a Sender Profile, with its own key or with `x-profile-id`, can't set `sender_profile` and is answered with a **400**.

**Changed: your organization's webhook receives only your organization's channel events.** A webhook subscribed to `channel` used to receive its Sender Profiles' channel events as well. A profile's channel events now reach only that profile's webhooks, including clones of yours.

- **Action required** if you expect your profiles' channel events at your organization's endpoint: add `"sender_profile": {"event_types": ["channel"]}` to the webhook.

#### MMS: One Attachment, a 600 KB Limit, and No Audio [#mms-one-attachment-a-600-kb-limit-and-no-audio]

Four changes to MMS on the v3 API. Each moves a failure that used to surface at the carrier, after the message was accepted and charged, to authoring time or to the send itself.

- **One attachment per message, down from 10.** `media_urls` on `POST /v3/messages` and a template's `mms.media` each take one item, and a second is rejected with `400`. A template saved with more than one attachment before this still sends, carrying only its first.
- **600 KB per attachment, checked before sending.** After accepting the message, Sent reads the size your server declares for the attachment with one `HEAD` request. Over the limit, an auto-detect send falls to SMS on the same number, with the attachment as a link when it fits, and a send pinned to `mms` fails. A size your server does not declare never blocks the send. See [Media Size Limits](/start/guides/mms#media-size-limits).
- **`audio` removed from the MMS media types.** A template media item declaring `audio` is rejected. Audio was never in the supported formats, so this moves a carrier-side failure to authoring time.
- **Media URLs must use a hostname.** A literal IP address is refused with `400`.

#### Sender Profiles: `billing.fallback` Removed, Plus Resend, Scheduled Sends, and MMS [#sender-profiles-billingfallback-removed-plus-resend-scheduled-sends-and-mms]

One removal and three additions on the v3 API, all live as of September 23, 2026.

**Removed: `billing.fallback` on Sender Profiles.** The `billing` object on `POST /v3/sender-profiles` and in the `GET /v3/sender-profiles` response now carries `inherit` only. Both schemas reject unknown fields, so a create request that still sends `billing.fallback` is answered with a **400** rather than having the field ignored. If you send it, drop it before your next call. Reading it from a response returns nothing, and the two-field shape it replaced could express a state the API never acted on, which is why it went rather than being deprecated in place.

- **Action required** if you call `POST /v3/sender-profiles` with an explicit `billing` object. Sending `{"inherit": ...}` alone is correct and unchanged.
- The field was published on August 31, 2026, so integrations written before then were never able to send it.

**Added: `scheduled_at` on `POST /v3/messages`.** Send a message at a future instant instead of now.

- Requires an **explicit UTC offset**, such as `2026-10-01T09:00:00+02:00` or `2026-10-01T07:00:00Z`. A timestamp without one is rejected with `400` rather than being read in the server's zone. The offset fixes the instant only, and the value is stored and echoed in UTC.
- Must be at least one minute ahead and at most 30 days ahead.
- An accepted message reports `SCHEDULED` and `GET /v3/messages/{id}` returns the release time.
- **Quiet hours, balance, and template approval are evaluated at release, not at acceptance.** A message accepted today can still fail at its release time, so treat `SCHEDULED` as queued rather than guaranteed.
- Omit the field to send immediately, exactly as before.

**Added: `mms` as a channel.** `mms` is accepted in `channel` and reported on messages and templates, and `POST /v3/messages` takes `media_urls` and `subject` alongside it. MMS is enabled per account rather than by request: until your account is enabled for it, an `mms` candidate is refused and routing falls back, so adding the channel to a send is safe to prepare ahead of time. MMS costs several times an SMS per message, which is why it is opt-in rather than inferred from a template carrying media.

#### Webhooks: the `channel` Family, Per-Attempt Signatures, and Rendered Bodies [#webhooks-the-channel-family-per-attempt-signatures-and-rendered-bodies]

Three changes to what a subscribed endpoint receives. A handler written against the previous behavior keeps working, but it now sees traffic and fields it did not see before.

**Added: the `channel` event family can be subscribed to.** Five sub-types follow one market from filing to sendable, so watching a sender go live no longer means polling `GET /v3/channels`: `channel.submitted`, `channel.changes_requested`, `channel.approved`, `channel.activated`, and `channel.deactivated`. The subject is always one market, never the account, and `payload.status` answers a different question from the sub-type: the sub-type says what happened, the status says whether the market can send. See [Event types](/start/webhooks/event-types) and [Lifecycle events](/start/webhooks/lifecycle).

- **Added**: `channel.activated` fires for every market that gains a sender, including markets that register with no regulator and senders assigned for you. Markets that previously raised no events at all raise them now, so expect volume on this family to go up rather than sideways.
- **Added**: `channel.deactivated` fires when a sender ID is cancelled for you, not only when a number returns to the pool or a campaign lapses.
- **Changed**: A sender ID that Sent pre-registers with the destination's regulator reports `channel.submitted` once that market's documents are in, and `channel.changes_requested` only while documents are outstanding. It previously reported `changes_requested` in both cases, which asked you to correct something that `GET /v3/compliance/requirements` reported nothing about.
- **Changed**: A 10DLC activation is announced when the campaign is put to work rather than when the registry's webhook lands, so a market that inherits its organization's campaign reports `channel.activated` too.

**Changed: every delivery attempt is signed at send time.** `X-Webhook-Timestamp` and `X-Webhook-Signature` are computed per attempt, so a retry carries its own timestamp and clears a 5-minute replay window however long the backoff ran before it. Both headers previously carried the event's creation time on every attempt, so a receiver enforcing that window rejected the later retries of an event that was only failing transiently. See [Signature verification](/start/webhooks/signature-verification).

- **Added**: `X-Webhook-Attempt` carries the index of the attempt in hand, starting at `1`, so a receiver can tell a redelivery from a first delivery without keeping state of its own.
- **Changed**: Deduplicate on `X-Webhook-Event-ID`, which holds one value for every attempt at the same event. A dedupe key built from the timestamp records one event once per attempt. See [Handling retries](/start/webhooks/handling-retries).

**Added: `body` on outbound message events.** Every `message.*` status event carries `payload.body`, the rendered message text as plain text, truncated at 3072 characters. The field is always present, and it is `null` when Sent is not asserting a body: before routing resolves a channel, on a send stopped before it got one, and on a delivery report for an attempt the message has since been rerouted away from. A non-null value is always the render for that event's own `channel`, so the two fields describe one attempt. The body is plain text, so a WhatsApp or RCS header, footer and buttons are not included; `GET /v3/messages/{id}` returns the full composed message.

**Added: `auto_reply_action` on templates.** `GET /v3/templates`, `GET /v3/templates/{id}` and the `templates` webhook events report which consent keyword a template answers when it is one of the auto-replies Sent creates for you: `OPT_IN`, `OPT_OUT`, `HELP`, or `OTHER` for a keyword you defined. The field is omitted for a template you authored, so its presence is the answer to whether the row or the event is about an auto-reply. Sent's three compliance auto-replies go through review like any other template, so their events arrive mixed in with your own, and nothing on the wire told them apart before.

**Templates: smaller changes.**

- **Fixed**: An RCS body truncated after variable substitution is cut on a character boundary, so a body with an emoji straddling the 3072-character limit no longer reaches the handset ending in a broken glyph.
- **Clarified**: `channels` on a template response lists every channel the definition's body can render on, following each channel's send-time fallback, which is why an `sms` and `whatsapp` pair reports `rcs` as well. It says what the content can render on, not what may be sent: sending also needs the template approved for that channel. The body, button and editing rules are in the [template definition reference](/reference/api/template-definition).

### August 2026 [#august-2026]

#### Sender Profiles, Channels, and Compliance Requirements [#sender-profiles-channels-and-compliance-requirements]

A profile is now created in one call, its senders are managed per market, and what a market demands is something you can ask for before you try.

**Added: `/v3/sender-profiles`.** `POST`, `GET`, and `GET`/`PATCH`/`DELETE` on `/{id}`. `POST /v3/sender-profiles` needs a `name` and a `short_name` and nothing else: identity, inbox, opt-out list, and billing come from your organization, so the profile is usable immediately with no compliance work. There is no completion step and no callback to receive. The response carries the profile's `api_key`, shown once and never returned again.

Every capability is one of three things, and there is no flag per state: supply the capability's fields to make it dedicated, send `{"inherit": true}` to take the organization's, or omit the block for neither. A read returns `channels.sms` as a list, with a status and outstanding compliance per market.

**Added: `/v3/channels`.** `GET /v3/channels` returns every market you send SMS in, your WhatsApp account, and your RCS agent, each with its own status. `POST /v3/channels/sms` adds a market (a country plus a sender type) and takes everything that market registers in one `compliance` object. `GET`/`PATCH /v3/channels/sms/{country}/{type}` read and correct one market; the `PATCH` is partial at every level, so an omitted key is left alone, an explicit `null` clears it, and `{}` is refused rather than silently accepted. `POST /v3/channels/whatsapp` connects an account shared through a Multi-Partner Solution, and `POST /v3/channels/rcs` requests an agent.

- **Added**: Status is per channel, never flattened onto the account or the brand: `PROVISIONING`, `ACTION_NEEDED`, `PENDING_REVIEW`, `ACTIVE`. A sender live in one country and mid-registration in another reports exactly that.
- **Changed**: `POST /v3/channels/whatsapp` does not accept `access_token`, `solution_id`, or `owner_business_id`. The first two are Meta's answer about provenance, and the token rotates roughly every sixty days, so all three are resolved from your organization.

**Added: `GET /v3/compliance/requirements`.** Call it first. It returns what a channel, country, and sender type demand (each requirement keyed as you write it, such as `brand.legal_name` or `campaign.message_flow`), plus `setup[]`, the calls that satisfy them with a body you can copy and send as it stands. It is the same declaration that validates the calls themselves, so it cannot drift from what the API accepts. `channel` defaults to `sms`; `whatsapp` and `rcs` return `501` until their requirements are declared, because an empty requirement set would wrongly say those channels demand nothing.

**Deprecated: `/v3/profiles` and the profile-campaign endpoints.** All eleven operations still behave exactly as before, so nothing breaks today.

- **Deprecated**: `POST`/`GET /v3/profiles`, `GET`/`PATCH`/`DELETE /v3/profiles/{profileId}`, and `POST /v3/profiles/{profileId}/complete`. Use `/v3/sender-profiles`.
- **Deprecated**: `POST`/`GET /v3/profiles/{profileId}/campaigns` and `PUT`/`DELETE /v3/profiles/{profileId}/campaigns/{campaignId}`. A campaign is a registration rather than a collection, so it now travels in `compliance.campaign` on the market call, one per market.
- **Deprecated**: `DELETE /v3/contacts/{id}`. Use `PATCH /v3/contacts/{id}` with `{"opt_out": true}`, which stops every send and keeps the record of who the contact was and that they asked.

**Changed: contact and template sharing between Sender Profiles is gone.** A profile sees only its own contacts and templates; the organization still sees those of every profile beneath it, through read-time widening. A tenant's customer data can no longer become visible to a sibling tenant by configuration.

**Changed: sender borrowing is gone.** A profile cannot be pointed at another profile's number. Give it a dedicated sender with `channels.sms`. Where `sending_phone_number_profile_id` is still populated on a read, such as `GET /v3/me`, it reports which account holds the number in inventory rather than a sender you can choose.

Six fields are now **accepted and ignored** rather than refused, because a `400` would break an integration that is otherwise working. They stay on the wire so a generated client keeps compiling, and every request carrying one is logged so they can eventually go for real:

| Field | Where | Reads back |
| --- | --- | --- |
| `inherit_contacts`, `inherit_templates` | `POST`/`PATCH /v3/profiles`, profile and organization responses | `false` |
| `allow_contact_sharing`, `allow_template_sharing` | The same | `false` |
| `sending_phone_number_profile_id`, `sending_whatsapp_number_profile_id` | `PATCH /v3/profiles/{profileId}`, profile responses | `null` |

- **Changed**: `is_inherited` on the contact response is always `false`. It stays on the wire so existing clients keep deserializing; do not branch on it.
- **Changed**: Inherited contacts are no longer read-only. The gate that rejected an update or a delete of one is gone, along with the contact rows it protected.
- **Changed**: An invalid `default_channel` on `PATCH /v3/contacts/{id}` now returns an invalid-enum error naming the accepted values rather than a generic validation failure.
- **Changed**: `primary_use_case` on the brand is always `null`. The campaign's use cases replace it.
- **Changed**: `is_welcome_playground` on `GET /v3/templates` is accepted and ignored. The filter it drove was removed.
- **Changed**: `GET /v3/me` no longer returns a stubbed organization in sandbox mode, and the four sharing settings are gone from its `profiles` entries.
- **Unchanged**: `POST /v3/messages` still has no synchronous `402`. Its declared responses are now `202`, `400`, `401`, `403`, `404`, and `500`, which matches the asynchronous balance gate the docs have described since July: the send is accepted with `202` and the affected messages are reported as `BLOCKED`.

**Migration:** Nothing is required today. When you move, start from `GET /v3/compliance/requirements` for the market you need, create the profile with `POST /v3/sender-profiles`, and add its sender with `POST /v3/channels/sms`. Check existing code for the six ignored fields above: a write to any of them still returns success and does nothing, and reading the value back is how you can tell. See [Create and activate Sender Profiles via the API](/start/advanced/sender-profiles-api) and [Managing channels](/start/guides/managing-channels).

#### Brands: `csp_id` Deprecated [#brands-csp_id-deprecated]

`csp_id` on the brand object is deprecated and will be removed in a later release. It's marked `deprecated` in the [OpenAPI specification](/reference/api/openapi-spec).

The field identifies the Campaign Service Provider that registered the brand, which is Sent, so the value is the same for every brand and every account. There's no action it supports and no replacement. Stop reading it.

- **Deprecated**: `csp_id` on the brand embedded in `POST /v3/profiles`, `GET /v3/profiles`, and `GET`/`PATCH /v3/profiles/{profileId}`.
- **Unchanged for now**: the field is still returned and still populated, so nothing breaks today. Removal lands in a later release with its own entry here.

Your own TCR identifiers are unaffected. `tcr_brand_id` and `universal_ein` stay.

#### Two-Way Conversations: Free-Form Gating on SMS and RCS [#two-way-conversations-free-form-gating-on-sms-and-rcs]

Free-form sends on SMS, RCS, and auto-detect are now governed by an explicit conversation rule rather than a one-time prior-inbound check.

- **Added**: A contact who has **ever** replied, on any channel and at any point in the past, can be sent free-form text indefinitely. A reply is treated as consent to converse and does not expire; only an opt-out ends it.
- **Added**: For a contact who has **never** replied, free-form rides on the last approved template you sent and lapses **7 days** after it. The cap exists to stop a one-sided stream of free-form content opened by a single template. Previously a contact who had never replied could not be sent free-form text at all.
- **Added**: `CONVERSATION_TEMPLATE_REQUIRED`, a dedicated code for that blocked case. It replaces the `VALIDATION_004` (`'template' is required`) this case previously produced, which read as a malformed request when the request was fine. The two message variants distinguish a contact with no template ever sent from one whose template has lapsed. Like the other send-time codes, the code itself is recorded internally rather than returned in API responses or webhook payloads.
- **Added**: Free-text, an account-level waiver of the conversation rule. With it enabled, free-form reaches a contact who has never replied on SMS, RCS, and auto-detect, with no template first and no 7-day window. It applies on each channel where the account has an active sender, it is set on the organization and inherited by Sender Profiles, and it changes neither Meta's 24-hour window nor opt-out enforcement. Sent enables it on request.
- **Changed**: The blocked send is recorded as **`BLOCKED`, not `FAILED`**. The gate runs before routing, so nothing is handed to a carrier: these messages are excluded from your deliverability rate and fire `message.blocked` rather than `message.failed`.
- **Changed**: A free-form send with `channel` omitted no longer fails when Meta's WhatsApp window is shut. WhatsApp is treated as unreachable for that send and the message falls back to RCS or SMS. A send pinned to `channel: "whatsapp"` still fails with `WHATSAPP_TEMPLATE_REQUIRED`, which remains a `FAILED` status.
- **Changed**: The `message.blocked` webhook event description now covers all three of its causes (account precondition, template not approved for sending, and no open conversation) rather than account preconditions alone. Description only: no subscription changes, nothing to re-subscribe.
- **Unchanged**: Meta's 24-hour customer-service window. Only an inbound WhatsApp message from the contact opens it; an outbound template never does. A send pinned to `channel: "whatsapp"` answers to that window alone.
- **Unchanged**: Opt-out keywords do not count as engagement, on either leg of the exchange. `START` and `HELP` do.
- **Unchanged**: `VALIDATION_004` itself. It remains the code for a genuinely missing required field, returned as `400` on the request.

**Migration:** If you branch on `VALIDATION_004` to detect a blocked free-form send, that branch no longer fires. If you subscribe only to `message.failed` to catch these, subscribe to `message.blocked` as well: the send is accepted with `202` and the message finalizes as `BLOCKED`. Contacts who have replied to you at least once need no action, since free-form to them is never blocked by this rule.

### July 2026 [#july-2026]

#### 10DLC: Messaging Volume Moved to Campaign (Breaking Change) [#10dlc-messaging-volume-moved-to-campaign-breaking-change]

Expected messaging volume is now a per-campaign field, not a brand-level attribute. Volume drives the TCR tier classification (low-volume vs. standard) and the monthly campaign fee. These are per-campaign concerns: a brand can have multiple campaigns at different tiers.

- **Removed**: `expected_messaging_volume` from `BrandComplianceInfo` (brand request body) and `BrandComplianceResponse` (brand response). The field is no longer accepted or returned on any brand endpoint.
- **Removed**: The dedicated update-brand-volume endpoint has been deleted. There is no replacement at the brand level.
- **Added**: `volume` field on campaign create (`POST /v3/profiles/{profileId}/campaigns`), update (`PUT /v3/profiles/{profileId}/campaigns/{campaignId}`), and get (`GET /v3/profiles/{profileId}/campaigns`) endpoints. The value is a numeric string representing expected daily message volume (for example `"1500"`). Values strictly below `2000` register the campaign at the low-volume tier (capped at 2,000 messages/day, lower monthly fee); `2000` and above register as standard. The field is optional, and omitting it registers the campaign as standard, the higher-fee tier, rather than returning an error.
- **Changed**: When updating a campaign's `volume` causes a tier change, the billing delta for the current window is applied immediately rather than being deferred to the next billing sweep.

**Migration:** Move `expected_messaging_volume` from brand requests to the `volume` field on each campaign request. Set `volume` explicitly on every low-volume campaign. A request that still sends the brand-level field is accepted and that field is ignored, so a campaign left without `volume` registers as standard and bills at the higher monthly fee, with nothing surfaced to flag it.

| Before | After |
|---|---|
| `BrandComplianceInfo.expected_messaging_volume` (brand request body) | `CampaignData.volume` (campaign create/update body) |
| `BrandComplianceResponse.expected_messaging_volume` (brand response) | `TcrCampaignWithUseCasesResponse.volume` (campaign response) |
| Single value shared across all campaigns under a brand | Set independently per campaign |

#### Message Status Model: New Values [#message-status-model-new-values]

Three new `MessageStatus` values have been introduced to distinguish policy-driven suppression from delivery failures:

- **Added**: `FILTERED`: message suppressed by a DENY routing rule before reaching a carrier. Policy-driven and expected. Does **not** count against your deliverability rate. The specific policy that stopped the send is recorded internally and is not returned in API responses or webhook payloads. Webhook event: `message.filtered`.
- **Added**: `BLOCKED`: message gated before send evaluation due to an account-level condition such as insufficient balance, an unmet onboarding entitlement, or a template that is not approved for sending. Does **not** count against your deliverability rate. The specific condition is recorded internally and is not returned in API responses or webhook payloads. Webhook event: `message.blocked`. Sends from a suspended account are rejected at the API edge with `403` and code `BUSINESS_014` and never create a message record, so they do not produce this status.
- **Added**: `SCHEDULED`: message queued for future delivery (curfew window or scheduled send). Not a terminal state; it transitions to `ROUTED` once the window opens. The release time is not exposed as an API field. Webhook event: `message.scheduled`.

**Migration note:** Prior to this release, all non-delivered outcomes were surfaced as `FAILED`. If your integration filters on `FAILED` to catch all unsent messages, also handle `FILTERED` and `BLOCKED` to maintain full coverage. `FILTERED` and `BLOCKED` are excluded from the deliverability rate denominator, so only `FAILED` counts against the rate.

| Old behavior | New behavior |
|---|---|
| `FAILED` covered all non-delivered outcomes | `FAILED` = downstream delivery attempt that failed (carrier/network) |
| No equivalent | `FILTERED` = suppressed by a DENY rule, which is policy-driven rather than a failure |
| No equivalent | `BLOCKED` = gated by an account condition before send |
| No equivalent | `SCHEDULED` = deferred to a future window (transient, not terminal) |

#### Message Scheduling & Quiet Hours [#message-scheduling--quiet-hours]

- **Added**: Messages destined for a mobile network with quiet-hours restrictions are now automatically deferred (status `SCHEDULED`) instead of being sent or failed during the restricted window, and released once it ends.
- **Fixed**: Quiet-hours windows that span midnight are now evaluated correctly.

#### Delivery Reliability [#delivery-reliability]

- **Added**: SMS messages that fail delivery on their original channel are now automatically retried on an alternate channel. This automatic fallback now also covers WhatsApp messages that can't be delivered.
- **Fixed**: A delivery receipt from a carrier could occasionally be matched to the wrong send attempt after a message was retried across channels, leaving its status stuck. Delivery status now updates correctly in this case.
- **Fixed**: `message.received` webhook events were not firing for some inbound WhatsApp and SMS auto-reply messages, and for messages sent to shared/ported numbers or redelivered inbound messages. These now fire correctly.

#### Compliance & Consent [#compliance--consent]

- **Added**: WhatsApp contacts who send a keyword command (`STOP`, `START`, `HELP`) now automatically receive a reply, and a `STOP` reply updates the contact's `opt_out` status as returned by `GET /v3/contacts/{id}`.
- **Updated**: Stricter validation now applies to `AUTHENTICATION`-category WhatsApp template bodies for the SMS channel, and for link/URL variables.

#### API Reliability & Security [#api-reliability--security]

- **Fixed**: Sending a free-form (non-template) message with `channel` omitted (auto-detect) could bypass the conversation-window gate that normally restricts free-form SMS/RCS sends to an active conversation. Auto-detect sends are now gated the same as explicit-channel sends.
- **Fixed**: Authentication-failure lockouts (`429`) are now scoped to the specific API key rather than the caller's IP address, so a customer sharing an IP with another tenant is no longer at risk of being locked out by unrelated failed attempts.
- **Fixed**: `DELETE /v3/templates/{id}` could fail for templates with channel-status or WhatsApp update-history records; deletion now cleans these up first.

#### Dashboard [#dashboard]

- **Added**: Sign in and sign up with Google, GitHub, or Facebook, in addition to email and password.
- **Added**: A new bulk-messaging tab in the Playground lets you upload a CSV of recipients and send to the whole list at once, with upfront validation of phone number formats.
- **Added**: Message activity now shows a segment count (for example, "3 parts") for multi-part SMS messages.

---

### June 2026 [#june-2026]

#### Conversations [#conversations]

- **Added**: New `GET /v3/conversations` and `GET /v3/conversations/{id}` endpoints to list a customer's messages grouped by conversation, with pagination.

#### WhatsApp Messaging [#whatsapp-messaging]

- **Added**: `POST /v3/messages` now accepts a plain-text `text` field as an alternative to `template`, for free-form WhatsApp messages within the 24-hour customer-service window. Sending free-form text outside that window now returns a dedicated `WHATSAPP_TEMPLATE_REQUIRED` error.
- **Added**: WhatsApp templates can now be approved and sent per channel independently. A template pending or rejected on one channel no longer blocks sending on a channel where it's approved. Sending on a channel where the template isn't active now returns a dedicated `BUSINESS_012` error.
- **Fixed**: Templates approved without a connected WhatsApp Business Account (for example, compliance-approved for SMS only) can now actually be sent, instead of being blocked for lacking a WhatsApp template ID.

#### Billing Accuracy [#billing-accuracy]

- **Fixed**: Multi-part SMS messages (over the 160-character GSM segment limit) are now billed per segment rather than as a single message.
- **Fixed**: WhatsApp messages billed directly by Meta to your WhatsApp Business Account are now only charged the difference against Sent's own price for that message, preventing double-charging.
- **Updated**: The recurring per-contact messaging charge now runs on a rolling 28-day cycle from the last charge, rather than resetting on the first of each calendar month.
- **Fixed**: Corrected per-network SMS cost resolution to always use the actual matching rate for a destination.

#### 10DLC Compliance [#10dlc-compliance]

- **Added**: `GET` campaign responses now include a `pricing` object (the resolved recurring campaign fee) and a flag indicating whether the one-time submission fee has been charged.
- **Updated**: 10DLC campaign submission and recurring maintenance fees are now billed on each campaign's own activation anniversary, rather than a shared calendar cycle.
- **Fixed**: Campaign submission fees that were missed on a brand resubmission are now correctly backfilled and charged.
- **Fixed**: Campaign activation now reliably registers the connected phone number with the carrier, so an approved campaign is actually enabled for sending.

#### Reliability [#reliability]

- **Fixed**: WhatsApp Business Account health is now determined the same way across onboarding, Meta webhooks, and send-time checks, reducing inconsistent "WhatsApp degraded" errors.
- **Fixed**: SMS delivery status is no longer marked `DELIVERED` as soon as a carrier accepts a message for transit. It now stays in transit until an actual delivery or failure signal arrives.
- **Fixed**: Contact opt-out (`STOP`) handling is now unified onto a single consent record, so a contact's opt-out status is consistent regardless of which channel they opted out on. `HELP`/`STOP` compliance auto-replies are no longer blocked by a contact's own opt-out status.
- **Fixed**: A deny routing rule with no fallback configured is now a hard block, instead of occasionally falling through to another route and sending anyway.

#### Dashboard [#dashboard-1]

- **Added**: Sub-account (Sender Profile) SMS configuration and pricing can now automatically inherit from the parent organization's defaults.
- **Added**: Self-service auto-recharge: enable auto-charge to automatically top up your balance from a saved card when it drops below a chosen threshold.
- **Added**: A restructured Brand Registration (10DLC) wizard for compliance onboarding.
- **Added**: Dedicated Sender Identity requests now support uploading required registration documents directly, with document-type status shown in the flow.
- **Added**: Campaign details now offer an AI-assisted quality check and rewrite of your campaign messaging.

---

### May 2026 [#may-2026]

#### Pre-Send Consent Gate [#pre-send-consent-gate]

<Callout type="warning">
**Superseded**: Consent-blocked messages are finalized as `FILTERED`, not `FAILED`, and surface on the `message.filtered` webhook. `POST /v3/messages` no longer rejects a send over recipient opt-out state: the all-recipients-opted-out case below is also accepted with `202` and blocked asynchronously per message. See the [error catalog](/reference/api/error-catalog).
</Callout>

- **Added**: New `ERR_CONSENT_BLOCKED` send-time error code. Every outbound message now runs through a pre-routing consent check that refuses sends to recipients with `opt_out = true` or whose phone is on the customer's phone-channel suppression list. Blocked messages are finalized as `FAILED` before any provider call is made, so no carrier charge applies. Inspect `description` on the message detail or in `GET /v3/messages/{id}/activities` to see the reason.
- **Updated**: `BUSINESS_004` is now scoped to the **all-recipients-opted-out** case. When *some* recipients are still reachable, the API accepts the batch and only the blocked recipients fail asynchronously with `ERR_CONSENT_BLOCKED`. See [API Errors](/reference/api/errors) and the [error catalog](/reference/api/error-catalog).

#### Inbound Message Webhooks [#inbound-message-webhooks]

- **Fixed**: `message.received` webhook events now fire correctly for inbound messages across all channels. Previously, subscribing to `message.received` produced no deliveries despite the event appearing in the subscription list. The webhook notification was only sent for outbound status changes. All inbound messages persisted since this release trigger a `message.received` event to your webhook endpoint.
- **Updated**: `message.received` payload `channel` field now reflects the actual inbound channel (`sms` or `whatsapp`). WhatsApp replies fire the same `message.received` event shape as SMS replies.
- **Fixed**: Inbound WhatsApp replies now reliably resolve to the correct account when a number has been used across multiple WhatsApp Business Accounts.

#### Profile Completion API [#profile-completion-api]

- **Updated**: `POST /v3/profiles/{profileId}/complete` now returns distinct typed responses:
  - **200**: Profile was already in a completed state. Response body: `{success: true, data: {status: "completed", message: "..."}}`.
  - **202**: Completion accepted and running in the background. Response body: `{success: true, data: {message: "..."}}`. The provided webhook URL is called when processing finishes.
  - Previously both paths returned an opaque `object` type, which made it difficult to distinguish synchronous completion from asynchronous processing in generated SDK clients.

#### API Schema [#api-schema]

- **Updated**: `event_data` and `metadata` fields on webhook event and message objects are now typed as open JSON objects in the OpenAPI spec. This resolves ambiguity in generated SDK clients where these fields previously appeared as untyped empty schemas. Runtime behaviour is unchanged.

#### Webhook Payload Standardization [#webhook-payload-standardization]

- **Updated**: Standardized the message webhook payload shape. The event-type field is now named `event` (was `sub_type`). Inbound message payloads: `from`/`to` renamed to `inbound_number`/`outbound_number`, the `provider` field was removed, and `updated_at` was added. Outbound message payloads gained `updated_at` and `template_name` fields.
- **Updated**: `message.sent` now reflects successful submission to the upstream provider; provider-side acknowledgement signals that previously could report as `message.sent` now resolve to `message.delivered`, so you see one clear status after submission (a later `message.failed` can still follow). `message.read` webhooks now cover WhatsApp and RCS (previously WhatsApp only), and are never emitted for SMS.

#### WhatsApp Template Reliability [#whatsapp-template-reliability]

- **Fixed**: Several classes of WhatsApp template were silently stuck and never actually submitted to Meta for approval: default compliance auto-reply templates (`STOP`/`START`/`HELP`), templates copied from the template library, and templates in a bulk submission with an empty name or unresolved language. These now submit correctly, and previously stuck templates were backfilled.
- **Added**: WhatsApp template URL buttons now support a dynamic variable in the button URL, for per-recipient personalization.

#### Compliance & Reliability [#compliance--reliability]

- **Fixed**: Inbound SMS opt-in (`START`) keywords are now only honored when the receiving number is currently assigned to your account, preventing consent from being recorded incorrectly after a number is reassigned or released.
- **Fixed**: A cross-provider configuration bug could let one SMS provider's delivery/webhook settings bleed into another's, affecting delivery status and webhook routing for some numbers. Resolved.
- **Fixed**: Messages that failed before a channel was selected now report the actual (or auto-routed) channel instead of the placeholder value `unknown`.

---

### April 2026 [#april-2026]

#### Opt-In / Opt-Out Keyword Management [#opt-in--opt-out-keyword-management]

- **Added**: Per-account keyword management for SMS opt-in and opt-out flows. You can now configure custom keywords (beyond the standard STOP/START/HELP) that trigger automatic replies and consent state changes. Contacts who send an opt-out keyword are automatically suppressed from future messages.
- **Added**: Inbound keyword matches now trigger configurable auto-replies, billed as standard outbound messages.

#### Inbound Message Processing [#inbound-message-processing]

- **Added**: Inbound messages from contacts are now persisted and fully tracked across all supported channels. Each inbound message appears in your message history with `direction: "INBOUND"` and `status: "RECEIVED"`.
- **Added**: Inbound messages generate a `message.received` webhook event. Subscribe to this event to receive real-time notifications when contacts reply to your messages. See [webhook event types](/start/webhooks/event-types) for payload details.
- **Added**: The `from` field is now captured on all message activities, so you can see the sender's phone number throughout the full message lifecycle.

#### Webhook Event Filtering [#webhook-event-filtering]

- **Added**: Granular webhook event filtering via the `event_filters` field. When creating or updating a webhook, you can now specify which message sub-types to receive per event type (for example, only `delivered` and `failed`) instead of subscribing to all status transitions. This reduces webhook volume for high-throughput integrations.

---

### March 2026 [#march-2026]

#### Template Approval Enforcement [#template-approval-enforcement]

- **Added**: Messages using WhatsApp templates that have not been approved by Meta are now blocked before dispatch, with a clear error response. Previously, unapproved templates could reach the provider and produce a delayed failure. Approved templates continue to send without any change.

#### OTP Delivery via WhatsApp [#otp-delivery-via-whatsapp]

- **Added**: OTP codes can now be delivered via WhatsApp. The platform waits for a delivery confirmation before reporting success, and automatically falls back to SMS if WhatsApp delivery is not confirmed within the timeout window. No API changes required. Channel selection follows your normal routing configuration.

#### Account Suspension [#account-suspension]

- **Added**: Accounts flagged as suspended are blocked from sending messages and receive a clear `account_suspended` error response on all API calls. This applies to both the messaging API and webhook delivery.

#### Error Documentation Links [#error-documentation-links]

- **Updated**: All API error responses now include a `doc_url` field pointing to the relevant documentation page for that specific error code. This makes it easier to diagnose and resolve integration issues without searching the docs manually.

#### Message Metadata [#message-metadata]

- **Added**: Messages now carry a `metadata` object that captures origin context (for example, the API endpoint that created the message). This field is returned in message detail and activity responses as an open JSON object.

---

### February 2026 [#february-2026]

#### Per-Customer Pricing [#per-customer-pricing]

- **Added**: Two billing models are now supported: **Active Contact** (charged per unique contact reached in a billing period) and **Per Message** (charged per message sent). Your account's billing model is configured at account setup. Charges are deducted automatically after each successful send.

#### Number Provisioning [#number-provisioning]

- **Added**: Phone numbers associated with your account are now visible via the API. Use `GET /v3/numbers/lookup/{phoneNumber}` to retrieve carrier and capability information for any number.

#### Playground Message Endpoint [#playground-message-endpoint]

- **Added**: A dedicated endpoint for sending test messages during onboarding, without requiring a fully provisioned profile. Useful for verifying end-to-end message delivery before going live.

---

### January 2026 [#january-2026]

#### Organizations & Sender Profiles (Multi-Tenancy) [#organizations--sender-profiles-multi-tenancy]

- **Added**: Full multi-tenancy support via Organizations and Sender Profiles. An Organization is the top-level account; Sender Profiles are sub-accounts that can inherit or isolate contacts, templates, brands, and campaigns from the parent organization.
- **Added**: Profile CRUD: create, list, retrieve, update, and delete Sender Profiles via the API.
- **Added**: `POST /v3/profiles/{id}/complete`: trigger the compliance setup workflow for a profile (TCR registration, WhatsApp connection).
- **Added**: Contact and template inheritance: profiles can be configured to share contacts and templates with the parent organization (`inheritContacts`, `inheritTemplates`), or to maintain their own isolated sets.
- **Added**: Template sharing: templates created at the organization level can be shared with child profiles without duplication.

#### User Management [#user-management]

- **Added**: Full user management for your organization:
  - `GET /v3/users` / `GET /v3/users/{id}`: list and retrieve users
  - `POST /v3/users`: invite a user by email with a specified role
  - `PATCH /v3/users/{id}`: update a user's role
  - `DELETE /v3/users/{id}`: remove a user from the organization
- **Added**: Role-based access: `OWNER`, `ADMIN`, and `MEMBER` roles with appropriate permission scopes. Owners have implicit `ADMIN` access across all endpoints.
- **Added**: User invitation emails with organization and profile context included in the invitation link.

#### WhatsApp Template Synchronization [#whatsapp-template-synchronization]

- **Added**: WhatsApp templates are now automatically synchronized from your connected WhatsApp Business Account. Template status updates (approved, rejected, paused) are reflected in real time via webhook-driven sync. No manual re-import needed.
- **Added**: Template soft-deletion: when a WhatsApp Business Account is disconnected or deleted, all associated templates are soft-deleted rather than permanently removed, preserving message history.
- **Added**: AUTHENTICATION template category support, including OTP and COPY_CODE button types for one-time password flows.

#### Error Codes [#error-codes]

- **Added**: Error code system for message sending failures. Each failure now includes a machine-readable `error_code` field in the message activity, making it straightforward to programmatically distinguish temporary failures (retry) from permanent ones (suppress).

---

## 2025 [#2025]

No customer-facing API changes shipped in 2025. Development during the year went into the platform capabilities released in early 2026, including multi-tenancy (Organizations and Sender Profiles), user management, WhatsApp template synchronization, and the error code system. See the [January 2026](#january-2026) entries for details.

---

## 2024 [#2024]

### December 2024 [#december-2024]

#### API v3 General Availability [#api-v3-general-availability]
- **Added**: Sent API v3 is now the recommended version for all integrations
- **Added**: Full API documentation for v3 endpoints
- **Added**: New getting started guide for v3

### November 2024 [#november-2024]

#### Webhook Endpoints [#webhook-endpoints]
- **Added**: `GET /v3/webhooks/event-types` endpoint to list available event types
- **Added**: `POST /v3/webhooks/{id}/test` endpoint to test webhook delivery
- **Added**: `POST /v3/webhooks/{id}/rotate-secret` endpoint for security rotation
- **Added**: `PATCH /v3/webhooks/{id}/toggle-status` endpoint to toggle webhook status

#### User Management [#user-management-1]
- **Added**: `GET /v3/users` and `GET /v3/users/{id}` for user listing and details
- **Added**: `POST /v3/users` to invite users to your organization
- **Added**: `PATCH /v3/users/{id}` to update user roles
- **Added**: `DELETE /v3/users/{id}` to remove users

### October 2024 [#october-2024]

#### 10DLC Compliance (Brands & Campaigns) [#10dlc-compliance-brands--campaigns]

<Callout type="warning">
**Superseded**: The standalone `/v3/brands` endpoints below no longer exist. Brand registration now flows through [Sender Profiles](/start/concepts/sender-profiles), and campaigns are managed under `/v3/profiles/{profileId}/campaigns`.
</Callout>

- **Added**: Brand registration endpoints for 10DLC compliance (superseded; brand registration now flows through Sender Profiles)
  - `POST /v3/brands` - Create brand
  - `GET /v3/brands` - List brands
  - `PUT /v3/brands/{id}` - Update brand
  - `DELETE /v3/brands/{id}` - Delete brand
- **Added**: Campaign management endpoints (paths since moved under Sender Profiles)
  - `POST /v3/brands/{id}/campaigns` - Create campaign (now `POST /v3/profiles/{profileId}/campaigns`)
  - `GET /v3/brands/{id}/campaigns` - List campaigns (now `GET /v3/profiles/{profileId}/campaigns`)
  - `PUT /v3/brands/{id}/campaigns/{id}` - Update campaign (now `PUT /v3/profiles/{profileId}/campaigns/{campaignId}`)
  - `DELETE /v3/brands/{id}/campaigns/{id}` - Delete campaign (now `DELETE /v3/profiles/{profileId}/campaigns/{campaignId}`)

#### Profile Management [#profile-management]
- **Added**: Full profile CRUD operations
  - `POST /v3/profiles` - Create profile
  - `GET /v3/profiles` - List profiles
  - `GET /v3/profiles/{id}` - Get profile details
  - `PATCH /v3/profiles/{id}` - Update profile
  - `DELETE /v3/profiles/{id}` - Delete profile
- **Added**: `POST /v3/profiles/{id}/complete` for profile setup completion

### September 2024 [#september-2024]

#### API v3 Beta Release [#api-v3-beta-release]
- **Added**: Core messaging endpoints
  - `POST /v3/messages` - Send messages
  - `GET /v3/messages/{id}` - Get message status
  - `GET /v3/messages/{id}/activities` - Get message activities
- **Added**: Contact management
  - `GET /v3/contacts` - List contacts
  - `POST /v3/contacts` - Create contact
  - `GET /v3/contacts/{id}` - Get contact
  - `PATCH /v3/contacts/{id}` - Update contact
  - `DELETE /v3/contacts/{id}` - Delete contact
- **Added**: Template management
  - `GET /v3/templates` - List templates
  - `POST /v3/templates` - Create template
  - `GET /v3/templates/{id}` - Get template
  - `PUT /v3/templates/{id}` - Update template
  - `DELETE /v3/templates/{id}` - Delete template
- **Added**: Webhook management
  - `GET /v3/webhooks` - List webhooks
  - `POST /v3/webhooks` - Create webhook
  - `GET /v3/webhooks/{id}` - Get webhook
  - `PUT /v3/webhooks/{id}` - Update webhook
  - `DELETE /v3/webhooks/{id}` - Delete webhook
  - `GET /v3/webhooks/{id}/events` - List webhook events
- **Added**: Number lookup
  - `GET /v3/numbers/lookup/{phoneNumber}` - Look up phone number information
- **Added**: Account information
  - `GET /v3/me` - Get authenticated account details

#### New Features [#new-features]
- **Added**: Sandbox mode (`sandbox: true`) for all mutation endpoints
- **Added**: Idempotency key support via `Idempotency-Key` header
- **Added**: Consistent JSON response envelope (`success`, `data`, `error`, `meta`)
- **Added**: Standardized error codes with documentation URLs
- **Added**: snake_case property naming convention
- **Added**: Rate limiting with detailed response headers

---

## 2023 [#2023]

### Legacy API v2 [#legacy-api-v2]

The v2 API remains fully supported for existing integrations. All v2 endpoints continue to operate at `/v2/` paths.

Key v2 endpoints:
- `POST /v2/messages/contact` - Send message to contact
- `POST /v2/messages/phone` - Send message to phone number
- `GET /v2/contacts` - List contacts
- `GET /v2/templates` - List templates

See [Legacy API Reference](/reference-legacy/api) for complete v2 documentation.

---

## Deprecation Notices [#deprecation-notices]

### API v2 [#api-v2]
- **Status**: Legacy (still supported)
- **Recommendation**: New integrations should use v3
- **End of Support**: No end date announced

---

<Callout type="info">
Subscribe to our [API Status](https://status.sent.dm) page for real-time updates on API changes and service status.
</Callout>

---

## Feedback [#feedback]

Have suggestions for API improvements? Contact [support@sent.dm](mailto:support@sent.dm).

---
