{% extends "_layout.html" %} {% set title = "Not acceptable" %} {% set status = "406 Not Acceptable" %} {% set description = "No representation satisfies your Accept. Often answered below the handler, untyped." %} {% block main %}
Your Accept header asks for nothing this endpoint can produce. Most of this API ignores Accept and sends its one representation, so this is rare.
application/json on the API, and text/event-stream at the log stream.An untyped answer is expected here. This refusal is often produced below the
request handler — by routing, the framework or a proxy — and then it arrives as the web
server’s own page, not as application/problem+json, and has no type
at all. Treat a non-problem+json 406 exactly as you would this type.
{
"type": "https://sc.example.com/server-errors/not-acceptable",
"title": "Not acceptable",
"status": 406,
"detail": "...",
"instance": "/v1/jobs/01J9...",
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
detail is prose and may be reworded at any time. Branch on type — never parse detail.
| any endpoint | Content negotiation, where a deployment does it. |
unsupported-media-type is about what you sent, not what you accept.