91305: Destination endpoint rejected the event

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.

• 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.

• 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.

• 91300: Event delivery to destination failed
• 91306: Destination endpoint returned a server error

• Data Destinations overview
• Create a destination
• Create a subscription