Errors

API-generated error responses use RFC 7807 problem details and the application/problem+json content type:

{
  "type": "https://example-data.com/errors/not-found",
  "title": "Not found",
  "status": 404,
  "detail": "No user with id=99999",
  "instance": "/api/v1/users/99999"
}

A HEAD request returns the same status and headers as GET, but its response body is empty as required by HTTP semantics.

Status codes

• 200 — successful read or simulated update
• 201 — simulated record creation
• 204 — successful preflight or simulated deletion, with no body
• 400 — invalid record id, malformed JSON, or invalid PATCH body
• 404 — record or collection not found
• 405 — HTTP method not supported by the resource
• 413 — request body exceeds 64 KiB
• 422 — POST or PUT body failed collection-schema validation
• 429 — Cloudflare edge rate limit exceeded; honor Retry-After
• 500 — unexpected server error

Problem types

The type member is a stable, dereferenceable URL. Open it for an explanation and suggested resolution.

• Bad request (400) — The request body is malformed JSON or is not the JSON shape required by the method.
• Invalid id (400) — A record endpoint received an id that is not a positive integer.
• Method not allowed (405) — The resource exists, but it does not support the requested HTTP method.
• Not found (404) — No record with the requested id exists in the selected collection.
• Payload too large (413) — The JSON request body exceeds the 64 KiB API limit.
• Unknown collection (404) — The requested collection is not registered by the API.
• Validation failed (422) — A POST or PUT body does not satisfy the collection schema.