Shipped
Developer documentation
Quickstart, guides, and a reference generated from the spec.
A developer documentation site: a quickstart, guides for headless mode, authentication and scopes, webhooks, conventions, test mode, and billing and meters, plus a per-operation reference for the whole /v1 surface.
Who it is for. The person deciding whether this gets integrated at all. Every dashboard action is a /v1 call, so the reference is the product rather than an integration surface bolted onto one — the API page makes that argument, and the docs are where you check it.
How it is built, and why that matters. The reference is generated from the same published OpenAPI document the dashboard’s own client is typed against, so every route in it is a route that answers, and it moves the day the API does. The error registry is generated the same way: every problem code the API returns resolves at the exact path its type URI points at.