Skip to main content
GET
Recover a Batch submission
Use this read-only endpoint after an idempotent Batch submission. The key is scoped to the authenticated owner and deployment. Reading its state never submits inference.
string
required
The submission’s UUID, written in canonical lowercase form.
string
required
Deployment API key in the form Key YOUR_SUTRO_API_KEY.

States

A known reservation returns HTTP 200. Inspect status and retryable even when the HTTP request succeeded.
HTTP 404 means this key has no reservation visible to the current owner in this deployment. Keep the same key when replaying an uncertain submission. The existing job status endpoint reports execution after acceptance; an accepted submission is not a completed job.

Check deployment capabilities

Before using durable submissions, read GET /v1/batch-capabilities with the same deployment key:
Require idempotent_submission: 1 and the formats your client uses. Upgrade an older deployment before submitting; do not fall back to an ordinary submission when relying on safe replay. The Python SDK and CLI perform this check. The CLI also preserves a local submission receipt automatically; Python callers persist their key and request configuration. submission_owner_id is the stable authenticated account ID. The CLI binds new receipts to it and verifies it before replaying an unresolved submission, so API key rotation for the same owner works while switching owners cannot create another job from the saved source.