Errors and integration checklist
| Result | Integrator action |
|---|---|
400 / 422 | Check query parameters, schema, canonical refs, checksums, and required headers against the operation contract. |
403 | Verify the hostname first; an unsigned GET to the IAM endpoint is not public. Check session expiry, signature scope, role permissions, repository allowlist, and public edge policy. |
404 | Confirm repository, branch, snapshot, run, artifact, or matching fingerprint exists and is visible. Current catalogs can be unpublished or tombstoned. |
409 | Inspect the error body for idempotency conflict, immutable/terminal state, or branch deletion. Do not retry changed content under the same key. |
429 / transient 5xx | Use bounded exponential backoff with jitter; preserve mutation identity and honor Retry-After when present. |
Not every operation returns every status above. See its reference entry and preserve the error body and request identifiers when seeking operator help. Redact AWS credentials and signed download URLs from logs.
Before shipping an integration:
- Choose the public or IAM hostname for each operation and environment.
- Discover valid branch refs and follow pagination without modifying cursors.
- Check run status and provenance before accepting a reusable result.
- Download before URL expiry and verify object integrity.
- Preserve mutation keys and run IDs across retries and workflow reruns.
- Treat upload, registration, finalization, catalog visibility, and validation evidence as separate steps.
The API reference is generated from the repository's OpenAPI contract during site build. Build validation compares the documented routes and anonymous access classification with Terraform's route groups. This checks source consistency; it does not establish that a particular infrastructure revision is deployed.