Error

error · 405

The fallback type for a status the API has no type for, and no route in the API sends it today.

Its slug says nothing about the cause, so status and detail are all it carries. A wrong method on a real path answers not-found, not 405.

This type adds no members to the ones every error carries.

Common causes

  • A status the API has no type for reached the error handler.

How to fix the call

  • Branch on status rather than on type for this one.
  • Read detail, and treat a 4xx as your bug and a 5xx as ours.
  • If you see this for a call, tell us with its requestId.

Example response

json
{
  "type": "error",
  "title": "Error",
  "status": 405,
  "detail": "Method Not Allowed",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects",
  "method": "PUT",
  "instance": "PUT /v1/projects",
  "docs": "https://ghaym.me/docs/errors/error"
}