{% extends "_layout.html" %} {% set title = "Method not allowed" %} {% set status = "405 Method Not Allowed" %} {% set description = "Wrong method for this path. Often answered below the handler, untyped." %} {% block main %}

The path exists, and not for the method you used. The response carries an Allow header listing the methods it does take.

What to do

  1. Read Allow and use one of those methods.

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

The body

{
  "type":     "https://sc.example.com/server-errors/method-not-allowed",
  "title":    "Method not allowed",
  "status":   405,
  "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 Routing.
{% 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-found is a path, or a thing, that is not there for you at all.

{% endblock %}