Errors

The Ingest API uses standard HTTP status codes. A successful submission returns 202 Accepted; any other response indicates that the request was not accepted and nothing was queued.

Status codes

Code	Meaning	Common cause
`202`	Accepted	The call was registered or queued for processing.
`400`	Bad request	The body failed validation: a missing required field, a wrong type, or an unexpected field (the body is strict).
`401`	Unauthorized	The API key was missing or not recognized. See Authentication.

Common mistakes

Extra fields. The request body accepts only the documented fields. Any additional key is rejected with 400, which catches typos such as recording_url in place of recordingUrl.
A recordingUrl that VOIX cannot reach. The URL you send must be fetchable by VOIX. A link that requires a session cookie, or that expires before VOIX retrieves it, will prevent transcription.

Retrying safely

Submissions are idempotent on callId. If a request fails with a network error or a 5xx response, you can resend it unchanged; the same callId updates the existing call rather than creating a duplicate. See Call lifecycle.