{% extends "_layout.html" %} {% set title = "Unsupported media type" %} {% set status = "415 Unsupported Media Type" %} {% set description = "A Content-Type this endpoint does not accept. Often answered below the handler, untyped." %} {% block main %}

The request body’s Content-Type is not one this endpoint accepts.

What to do

  1. Send application/json to the JSON endpoints.

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 415 exactly as you would this type.

The body

{
  "type":     "https://sc.example.com/server-errors/unsupported-media-type",
  "title":    "Unsupported media type",
  "status":   415,
  "detail":   "...",
  "instance": "/v1/jobs/01J9...",
  "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}

detail is prose and may be reworded at any time. Branch on type — never parse detail.

Where it comes from

any endpoint with a body
POST /v1/auth/device/{user_code} The approval leg takes application/json only.
{% include "_help.html" %}

At the two OAuth endpoints

Raised at POST /v1/auth/token and POST /v1/auth/device too, before any OAuth processing, and in problem+json there as everywhere — never as an OAuth error. A client handles it by its status and type.

What this is not

not-acceptable is about what you accept back.

{% endblock %}