Create a batch
POST/v1/batches
Submit an asynchronous batch job over an uploaded JSONL input file. DVARA can run a configured budget gate before dispatch and then relays the provider's batch object unchanged. Individual input lines execute at the provider and do not pass through DVARA's live chat policy, guardrail, routing, or response-PII pipeline.
Request
Responses
- 200
- 400
- 401
- 402
- 403
- 502
Created batch
The request was refused before dispatch: a body that is not valid JSON or has a field of the wrong type (invalid_json), a body that fails validation (validation_error, with the field names in param), an invalid body (invalid_request), no provider for the model (no_provider, no_capable_provider), an unsupported field or capability (unsupported_capability, unsupported_response_format), a request too large for the model's context window (context_window_exceeded), a PII BLOCK action (pii_detected), or the provider refused the request itself (provider_rejected_request).
No key was sent (api_key_required), or the key is unknown (invalid_api_key), revoked (api_key_revoked) or expired (api_key_expired).
A hard budget cap is exhausted (budget_cap_hard), the call would cost more than the per-call ceiling (per_call_cost_exceeded), or, without a licence, the monthly call band is used up (license_token_cap_exceeded, type token_cap_exceeded).
The key is valid but its nonempty scope list does not include batches:write (api_key_scope). On file upload and batch submit, a suspended workspace is also refused (workspace_suspended). On the Enterprise platform, upload and submit are also refused (policy_denied) when a JSONL line names a model the workspace may not use. The error names the first such line in line and custom_id.
Every configured provider on the route (and every fallback) has failed.