HTTP status code 415 — Unsupported Media Type
Quick answer
Status code 415 (Unsupported Media Type): Content-Type is not acceptable. Send the media type the API documents (e.g. application/json).
Send the media type the API documents (e.g. application/json).
415 is about Content-Type / body format, not Accept negotiation (that is closer to 406). Align headers with the API spec.
Common causes
- Sending form-data when the API expects application/json (or vice versa)
- Missing the Content-Type header entirely
How to fix it
Set Content-Type to exactly what the API docs specify, and make sure the body is actually encoded that way.
Related: 413418410409408422500502
Frequently asked questions
What is status code 415?
415 Unsupported Media Type: Content-Type is not acceptable. Send the media type the API documents (e.g. application/json).
When should I expect HTTP 415?
415 is about Content-Type / body format, not Accept negotiation (that is closer to 406). Align headers with the API spec.
What usually causes HTTP 415?
Sending form-data when the API expects application/json (or vice versa); Missing the Content-Type header entirely.
How do I fix HTTP 415?
Set Content-Type to exactly what the API docs specify, and make sure the body is actually encoded that way.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.