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

# 90032: Broadcast recipient's 'to' is invalid

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio could not process the broadcast recipient because the `to` value is not in a valid format. Set `to` to a channel and address pair in the format `channel:address`.

### Possible causes

* The `to` value does not include the required colon separator between the channel and address
* The channel name in `to` is missing or misspelled
* The address portion of `to` is empty
* The address does not match the expected format for the selected channel
* The request sends the recipient object with an incorrectly structured or malformed `to` field

### Possible solutions

* Update the recipient `to` value to use the required `channel:address` format
* Verify that the channel is valid for your Notify integration, such as `sms`, `whatsapp`, `facebook-messenger`, or another supported channel
* Confirm that the address is valid for the selected channel, such as an E.164 phone number for `sms` or `whatsapp`
* Review your request payload before sending it and reject recipients with missing or malformed `to` values
* If you generate recipient objects programmatically, add validation to ensure every `to` value includes both a channel and an address

#### Additional resources

* [Notify API overview](/docs/notify/api)
* [E.164 formatting](/docs/glossary/what-e164)
* [WhatsApp with Twilio](/docs/whatsapp)