Troubleshoot Capture API requests
Resolve authentication, validation, duplicate, rate-limit, and availability errors.
- For
- Workspace users and support owners
- Owner
- Integration engineering
- Outcome
- Identify the failure state, recover without duplicate work, or contact support with safe evidence.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Start from the visible symptom, the affected workspace, and the approximate time. Confirm the current state before repeating an action.
What you can see
- The API returns 400, 401, 409, 429, or 503.
- A person is rejected, captured twice, or mapped incorrectly.
- A bulk request is partly rejected or exceeds the supported size.
Check the current state
- Call GET /api/v1/capture/info with both required authentication headers.
- Validate the request against the published OpenAPI contract.
- Confirm the Idempotency-Key and whether the same logical request was already accepted.
- Review client state, rate limit, source, owner, and custom-field mappings.
Recover safely
- Correct a 400 request before retrying.
- Replace or reactivate credentials for a 401 response.
- For a 409 response, inspect the prior result before creating a new logical request.
- For 429 or 503, use bounded exponential backoff and preserve the same idempotency key for the same logical request.
Never put the API secret in browser code, public logs, screenshots, support chat, or documentation feedback.
Contact support
Send the workspace, page, approximate time, safe error code, expected result, actual result, and checks already completed.
- State whether you repeated the action and whether it can create an external side effect.
- Do not send passwords, tokens, API secrets, webhook secrets, message content, or unnecessary customer data.