Platform
Docs
Solutions
ContactLog In

Error: Twilio Error 12300

What's Causing This Error?

There are several Content-Types Twilio accepts. If Twilio cannot process the URL's Content-Types, it results in error 12300. Stating a Content-Type for a request is essential; otherwise, it would result in a 502 (Bad Gateway) error.

For example, attempting to play non-audio content like XML by having a Play verb is a cause for Twilio error 12300.

Read more about accepted Content-Types here.

Solution - Here's How To Resolve It

It would help if you verified that your web server returns the expected value as the Content-Type, and the URL refers to a valid and acceptable resource. In addition, you have to determine that the messages going to and from the Twilio phone number utilize a supported Content-Type.

Other Common Twilio Errors (and Solutions)

View all errors

Build your first notification in minutes

Send up to 10,000 notifications every month, for free.

Get started for free

Email & push notification

Build your first notification in minutes

Send up to 10,000 notifications every month, for free.

Get started for free

Email & push notification

Platform

Users

Content

Channels

Sending

Workflows

Preferences

Inbox

Workspaces

Observability

API Status

Changelog

© 2024 Courier. All rights reserved.