Skip to main content
GET
Read processing progress and terminal counts.
string
required
Opaque job identifier from the accepted response.

Job lifecycle

status is queued, processing, completed, completed_with_errors, or failed. The last three are terminal. completed means every item succeeded, completed_with_errors means some items succeeded and some failed, and failed means no item succeeded. A job whose products are all confirmed to have no ESA requirement starts as completed during submission. Its results are returned inline by the submission endpoint, so you do not need to poll it. counts reports queued, processing, succeeded, and failed items. started_at, completed_at, and expires_at can be null while work is pending. Results expire 30 days after terminal completion. Poll with backoff (for example, every five seconds). Responses use Cache-Control: no-store. A different provider or expired/unknown job receives 404 BULK_JOB_NOT_FOUND.

Errors

A malformed job UUID returns 422 INVALID_REQUEST. An unknown, expired, or other-provider job returns 404 BULK_JOB_NOT_FOUND. All routes can also return authentication, validation, rate-limit, and dependency errors. Use the error catalog and examples to choose a retry or correction. Keep X-Request-ID when present.