--- title: "HTTP 415 Unsupported Media Type — Meaning & Fix" description: "HTTP 415 Unsupported Media Type explained: what it means, common causes, how to fix it and how to monitor for it." url: https://uptrack.app/http/415 ---

# HTTP 415 Unsupported Media Type

The server refuses the request because the Content-Type header specifies a media type that the endpoint does not support. The payload format is not one the server is willing to accept. ## What does HTTP 415 mean? The server refuses the request because the Content-Type header specifies a media type that the endpoint does not support. The payload format is not one the server is willing to accept. ## Common causes 1. 1 Sending JSON to an endpoint that expects form data (application/x-www-form-urlencoded), or vice versa. 2. 2 Missing Content-Type header entirely. Some frameworks default to a type the endpoint does not accept. 3. 3 Uploading a file type the server does not support (e.g., sending a .webp image to an endpoint that only accepts .jpg and .png). ## How to fix it 1. 1 Set the correct Content-Type header: application/json for JSON, multipart/form-data for file uploads, application/x-www-form-urlencoded for form data. 2. 2 Check the API documentation for accepted media types. The response may include an Accept header listing supported types. 3. 3 If using fetch or axios, ensure the Content-Type is not being overridden by default settings or interceptors. ## Monitor for HTTP 415 errors A 415 on a previously working endpoint usually means a deployment changed the accepted content types. Uptrack monitors response codes so you catch these breaking changes quickly. ## Catch HTTP errors before your users do Start free, or choose a plan, for 30-second monitoring and alert confirmation. [See plans](https://uptrack.app/pricing) from $3/mo · 30-day money-back guarantee ## Other HTTP status codes - [HTTP 413 Payload Too Large](https://uptrack.app/http/413) - [HTTP 410 Gone](https://uptrack.app/http/410) - [HTTP 409 Conflict](https://uptrack.app/http/409) - [HTTP 408 Request Timeout](https://uptrack.app/http/408) - [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422) - [HTTP 405 Method Not Allowed](https://uptrack.app/http/405) - [HTTP 404 Not Found](https://uptrack.app/http/404) - [HTTP 403 Forbidden](https://uptrack.app/http/403) - [HTTP 401 Unauthorized](https://uptrack.app/http/401) - [HTTP 429 Too Many Requests](https://uptrack.app/http/429) - [HTTP 400 Bad Request](https://uptrack.app/http/400) - [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451) - [HTTP 500 Internal Server Error](https://uptrack.app/http/500) - [HTTP 502 Bad Gateway](https://uptrack.app/http/502) - [HTTP 503 Service Unavailable](https://uptrack.app/http/503) - [HTTP 504 Gateway Timeout](https://uptrack.app/http/504) - [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520) - [HTTP 522 Connection Timed Out](https://uptrack.app/http/522) - [HTTP 304 Not Modified](https://uptrack.app/http/304) - [HTTP 302 Found](https://uptrack.app/http/302) - [HTTP 301 Moved Permanently](https://uptrack.app/http/301) - [HTTP 204 No Content](https://uptrack.app/http/204) - [HTTP 201 Created](https://uptrack.app/http/201) - [HTTP 200 OK](https://uptrack.app/http/200)