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

# 90039: Broadcast 'MessageStatusCallbackUrl' is invalid

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you send a Bulk Messaging request with a `MessageStatusCallbackUrl` that is not a valid absolute callback URL. Twilio accepts only `http://` and `https://` schemas for messaging webhook URLs, and invalid request input is rejected as a `400` error.

### Possible causes

* The `MessageStatusCallbackUrl` uses an unsupported schema, or it does not include `http://` or `https://`.
* The `MessageStatusCallbackUrl` is not a fully qualified absolute URL, such as a relative path or a URL missing a hostname.
* The `MessageStatusCallbackUrl` contains malformed characters or improperly encoded URL components, which makes the callback URL invalid.

### Possible solutions

* Set `MessageStatusCallbackUrl` to a fully qualified `http://` or `https://` URL.
* Verify that the callback URL includes a valid protocol, hostname, and any required path or query parameters in a valid URL format.
* Use a publicly reachable endpoint for your callback URL. If you are testing locally, expose your application through a public HTTPS tunnel before sending the request.
* Resubmit the broadcast request after you correct the `MessageStatusCallbackUrl` value.

#### Additional resources

* [Getting started with Twilio Bulk Messaging](/docs/bulk-messaging/getting-started)
* [Operations and Message Tracking](/docs/bulk-messaging/operations-and-message-tracking)
* [Webhooks Overview](/docs/usage/webhooks/webhooks-overview)