Errors and troubleshooting
Understand TaskInfer HTTP errors without relying on provider-specific behavior.
TaskInfer returns standard HTTP status codes and neutral error messages. Public errors describe what the client can act on without exposing internal implementation details.
| Status | Meaning | What to check |
|---|---|---|
400 | Invalid request | Required fields, field values, and response-format constraints. |
401 | Invalid API key | The bearer header, key status, and workspace access. |
402 | Insufficient credits | Whether the workspace associated with the API key has available credits. |
413 | Upload too large | The uploaded file must not exceed 100 MB. |
502 | Inference request failed | Retry only when it is safe for your application to repeat the task. |
503 | Capability unavailable | The selected TaskInfer capability is temporarily unavailable. |
Insufficient credits
A 402 response means the workspace associated with the API key does not have enough credits for the request. Open the workspace list, select that workspace, and review its Billing page before retrying.
Common validation issues
Timestamps rejected
Set response_format=verbose_json whenever you send timestamp_granularities[].
Speaker labels rejected
Set both speaker_labels=true and response_format=verbose_json.
Upload rejected
Confirm the multipart field is named file and the uploaded payload is 100 MB or smaller.