Protocol mechanics the themed APIs do not cover: 202 Accepted with job polling, 301/302 redirects (and a chain), 503 with Retry-After, a guaranteed 504, Accept-based content negotiation with 406, HATEOAS links, RFC 6902 JSON Patch and 410 Gone.
The Protocol Lab is the catalog's HTTP semantics bench, and covers what most mock APIs never do: 202-accepted async jobs you poll to completion, 301 and 302 redirects, 503 and 504 outages, JSON Patch, and content negotiation that answers 406 when it cannot satisfy your Accept header. If a client library is going to surprise you, it will surprise you here.
Base URL: https://funapi.dev/api/protocol/v1 · 12 endpoints · OpenAPI 3.1 spec and Postman collection available. New here? Read the getting started guide.
202 Accepted + poll to completion
POST /protocol/v1/jobs — Start an async job — 202 AcceptedGET /protocol/v1/jobs/{id} — Poll a job — progresses on every poll301, 302 and a chain to follow
GET /protocol/v1/moved/old-dashboard — Permanently moved — 301GET /protocol/v1/moved/new-dashboard — Where the 301 leadsGET /protocol/v1/hop — A 302 redirect chain — follow it down503 & 504 on demand
GET /protocol/v1/maintenance — Scheduled maintenance — 503 + Retry-AfterGET /protocol/v1/gateway-timeout — Slow upstream — waits ~3s, then 504HATEOAS, JSON Patch, 406 & 410
GET /protocol/v1/export/documents — Content negotiation via Accept (406 on anything else)GET /protocol/v1/documents — List documents (HATEOAS links)GET /protocol/v1/documents/{id} — Get a document (410 after deletion)PATCH /protocol/v1/documents/{id} — RFC 6902 JSON Patch (op/path/value)DELETE /protocol/v1/documents/{id} — Delete a document (admin only, then 410) (requires Bearer auth)