Skip to the content

406 Not Acceptable

The server has no version of the resource that fits what the Accept headers of the request ask for.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

When the client says which formats, languages or encodings it takes, the server only has others, and it is strict about it. A request with Accept: application/xml to an API that only speaks JSON, for instance. Many servers aren't strict and send what they have with a 200.

What to do about it

Look at the Accept, Accept-Language and Accept-Encoding headers of the request and widen them, or leave them out. In an API client the culprit is usually an Accept header left over from the defaults of a library or from a copied example.

Not to be confused with

415 Unsupported Media TypeThe other direction: the server doesn't accept the format of what the client sent.
300 Multiple ChoicesThe server has several versions and lets the client choose.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12