---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/90033#article
headline: "90033: Broadcast recipient's 'to' is too long"
url: https://www.twilio.com/docs/api/errors/90033
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 90033: Broadcast recipient's 'to' is too long

Log Type: APPLICATION

Log Level: ERROR

## Description

The recipient `to` value in your Notify broadcast request is longer than the maximum length allowed for the selected channel. Twilio rejects the request when a destination address does not match the expected format or exceeds channel limits.

### Possible causes

* You sent a phone number, identity, or device address that is longer than the channel supports.
* The `to` value includes extra characters such as spaces, formatting symbols, or concatenated data that make the address invalid.
* You used the wrong destination type for the channel, such as sending a non-phone-number value for an `sms` or `mms` notification.
* Your application passed an unvalidated user-supplied value into the recipient list.

### Possible solutions

* Validate each recipient address before you send the broadcast.
* For `sms` and `mms`, send the destination as a valid phone number in `E.164` format.
* Make sure the `to` value matches the channel you selected and remove any unsupported prefixes, labels, or appended metadata.
* Review your application logic for string concatenation or serialization issues that can make the destination value too long.
* If you are sending to identities or bindings, confirm that the stored address or identity value is within the limits required by your Notify integration.

#### Additional resources

* [Notify API overview](/docs/notify/api)
* [Phone number formatting in E.164](/docs/glossary/what-e164)
* [Using Twilio phone numbers](/docs/phone-numbers)