---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/90034#article
headline: "90034: 'BroadcastStatusCallbackUrl' is too long"
url: https://www.twilio.com/docs/api/errors/90034
inLanguage: en
dateModified: 2026-06-08T11:38:30.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 90034: 'BroadcastStatusCallbackUrl' is too long

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when the `BroadcastStatusCallbackUrl` value in your bulk messaging request exceeds the allowed length. Twilio validates bulk messaging requests before processing them, so shorten the callback URL and resend the request.

### Possible causes

* The `BroadcastStatusCallbackUrl` value is longer than Twilio accepts for a request.
* The callback URL includes long query parameters, fragments, or encoded state.
* Your application appends campaign, recipient, or tracking data directly to `BroadcastStatusCallbackUrl`, which makes the URL too long.

### Possible solutions

* Shorten the `BroadcastStatusCallbackUrl` value before you send the request.
* Remove unnecessary query parameters, fragments, and embedded state from the callback URL.
* Keep the callback endpoint stable and use the `operationId` returned by the Bulk Messaging API to correlate status updates in your application.
* If you need operation updates without encoding extra context in the URL, subscribe to Bulk Messaging Events and map events to your internal records by `operationId` or `messageId`.

#### Additional resources

* [Bulk Messaging API](/docs/bulk-messaging)
* [Operations and Message Tracking](/docs/bulk-messaging/operations-and-message-tracking)
* [Bulk Messaging Events](/docs/bulk-messaging/events)