API Reference
Errors and recovery
Classify Capture API failures and choose a safe correction or retry.
- For
- Integration developers and support owners
- Owner
- Integration engineering
- Outcome
- Recover without duplicate captures or hidden failed work.
- Last verified
- 2026-09-01
- Next review
- 2026-11-30
- Status
- Supported public contract
| Status | Meaning | Client action |
|---|---|---|
400 | The request is invalid. | Correct it before retrying. Use a new key for corrected work. |
401 | The client is not accepted. | Repair or replace the server-side client. |
409 | The idempotency key conflicts with earlier work. | Inspect the earlier result. Do not bypass it. |
429 | The client rate limit is reached. | Wait and use bounded backoff. |
503 | Capture is temporarily unavailable. | Retry only when the response says the failure is retryable. |
Log only the endpoint, status, safe error code, request identifier, attempt number, and final outcome. Redact credentials and unnecessary customer fields.