Request and response conventions

Use the curated API reference for customer-facing operation contracts. Requests and responses are JSON where the operation declares JSON; uploads and downloads use the media types declared there.

Do not copy fields from examples into an integration unless the current schema declares them. Preserve response status, headers, and body when diagnosing an error. The API uses an ok field in several existing response shapes, but clients should follow the operation schema rather than assume one universal envelope.

The API base URL includes /api; do not duplicate or omit that prefix when constructing requests.