Get job
Read the current state of asynchronous work.
/jobs/{job_id}PermissionCluster key, or a scoped key with read (write includes read). Key scopes and actions.
- Use events webhooks for live status. Read the job to inspect its current state or recover after a missed event.
- A terminal job can be succeeded, failed, or canceled. Inspect error when a job fails.
Path parameters
Public job ID with the job_ prefix, returned by the operation that started the work.
Responses
200Success
The current job state. This example shows successful completion.
application/json
Response headers
The Engine request ID. Retain it when investigating a failed or unexpected request.
The X-Request-Id you sent, echoed when it is a valid ID. Otherwise, the Engine request ID.
Collection name when this job belongs to a collection. Otherwise omitted.
Time the resource was created, as an ISO 8601 UTC timestamp.
Failure details, or null when no failure is recorded.
File ID when this job acts on one file. Otherwise omitted.
Immutable job ID with the job_ prefix. Use it to read the current state.
Namespace name when this job belongs to a namespace.
Current state of the asynchronous work. succeeded, failed, and canceled are terminal states.
- queued
- Accepted and waiting to start.
- running
- Work is in progress.
- succeeded
- Work completed successfully.
- failed
- Work ended with an error.
- canceled
- Work ended after cancellation.
Kind of work accepted by the API.
- index_file
- Index a new or replacement file.
- delete_file
- Remove a file and clean its derived data.
- reindex_collection
- Rebuild the collection’s derived data.
- delete_collection
- Remove a collection and its derived data.
- delete_namespace
- Remove a namespace and its collections.
- apply_access_rule
- Apply changed governing rules to affected files.
- reindex_metadata
- Rebuild the metadata index after a change of the metadata fields.
Time the resource last changed, as an ISO 8601 UTC timestamp.
Errors
Select an error in the response example to see its JSON body. See error handling for the common error format.
- 400invalid_request
A field, path, parameter, or conditional request rule is invalid.
What to do: Correct the request. Unknown fields are rejected.
- 401unauthenticated
The API key is missing, invalid, or revoked.
What to do: Send an active key in Authorization: Bearer or X-API-Key.
- 403forbidden
The key can see the resource but lacks permission for this operation.
What to do: Use a key with the required action or scope kind.
- 404not_found
The resource is absent, deleted, or outside this key’s scope.
What to do: Check the identifier and the key’s namespace and collection scope.
- 500internal_error
An unexpected server failure prevented this request from completing.
What to do: Retain request_id for investigation. Follow retryable before retrying a write.