---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/91305#article
headline: "91305: Destination endpoint rejected the event"
url: https://www.twilio.com/docs/api/errors/91305
inLanguage: en
dateModified: 2026-11-04T19:15:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 91305: Destination endpoint rejected the event

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio records this error when Data Destinations attempts to deliver an event, but the target destination rejects the payload with an HTTP 4xx status code.

Because a 4xx response indicates a client-side or configuration error, Twilio does not attempt to retry delivery for these events.

### Possible causes

* Authentication or authorization failures (401 / 403): API keys, credentials, or signing signatures configured on the destination are invalid or expired.
* Invalid endpoint URL (404): The URL path configured on the destination is incorrect or the target route no longer exists.
* Payload or header rejection (400 / 415): The destination endpoint rejected the payload structure, missing parameters, or the `Content-Type` header sent by Twilio.
* WAF or firewall blocking: A Web Application Firewall (WAF), CDN, or bot protection layer blocked the incoming request before it reached your service application.

### Possible solutions

* Inspect your destination endpoint's logs to review the full request payload, headers, exact status code, and response body returned to Twilio.
* Verify that any API keys, tokens, or signing secrets configured on the destination match your destination's requirements.
* Confirm that the URL and path configured on the destination are active and correctly routed.
* If your endpoint sits behind a WAF or CDN, update firewall and WAF rules to ensure Twilio's IP ranges are allowed.
* Ensure your endpoint is configured to parse the content type (e.g., `application/json`) transmitted by Twilio for this destination type.

### Related errors

* [91300: Event delivery to destination failed](/docs/api/errors/91300)
* [91306: Destination endpoint returned a server error](/docs/api/errors/91306)

#### Additional resources

* [Data Destinations overview](/docs/data-destinations)
* [Create a destination](/docs/data-destinations/api-quickstart#create-a-destination)
* [Create a subscription](/docs/data-destinations/api-quickstart#create-a-subscription)