415
Unsupported Media Type
Client errors (4xx)·RFC 9110
What 415 means
The request’s media type is not supported by the resource.
For example, sending XML to an endpoint that only accepts JSON. Fix the Content-Type header and body format.
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long416Range Not Satisfiable417Expectation Failed418I'm a teapot421Misdirected Request422Unprocessable Content423Locked424Failed Dependency425Too Early426Upgrade Required428Precondition Required429Too Many Requests431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 415
What does HTTP 415 mean?
415 Unsupported Media Type: The request’s media type is not supported by the resource. For example, sending XML to an endpoint that only accepts JSON. Fix the Content-Type header and body format.
Which class does status code 415 belong to?
415 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 415 code defined?
Status code 415 is defined in RFC 9110 and is part of the IANA HTTP Status Code Registry.