415 Unsupported Media Type — Causes & Fix
HTTP 415 (Unsupported Media Type) means the server refuses the request because the body's media type (Content-Type) isn't supported by the endpoint.
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include sending the wrong Content-Type (e.g. text/plain where application/json is required), or an unsupported upload format. HTTP status 415 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "415 Unsupported Media Type" from an API
- A request/upload with the wrong format is rejected
How to fix it
- 1
Set the correct Content-Type
1. Send the media type the endpoint expects (e.g. Content-Type: application/json).
- 2
Convert the format
1. Convert the payload/file to a supported type before sending.
Frequently asked questions
Why 415 on my API call?
The Content-Type header doesn't match what the endpoint accepts. Set it to the required type (often application/json).
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.