The OpenAPI reference is generated from the gateway
2026-04-01 · Using the API
The reference page and the SDKs come from one spec, so the field names match.
/docs/reference is the rendered OpenAPI document. When a field exists there, the SDKs have it too, because both are generated from the gateway.
Do not hand-edit a client to add a field that is not in the reference. Unknown fields are a 422. If you need a field, it has to exist on the service first.
The task-style routes are left out of the generated SDKs on purpose. Those clients use /v1. A task-style caller uses the raw HTTP routes.
If the reference and a blog post ever disagree, trust the reference and the API guide. Those are generated and maintained with the code.
Ready to call it? Start with the quickstart, the API guide, or pricing.