List translation jobs

Find jobs by engine, status, trigger, or service key and follow cursor pagination.

List jobs visible to the caller in an organization:

http
GET /v2/organizations/:orgId/localization/jobs?limit=50
X-API-Key: YOUR_API_KEY

The response contains data, an array of job summaries, and meta.nextCursor. Follow nextCursor until it is null; an empty page alone is not a substitute for inspecting the cursor.

Filters #

ParameterMeaning
engineIdsEngine IDs to include.
statusesPending, Running, Completed, Failed, or Cancelled.
triggersapi, cli, ci, github, payload, or zendesk.
apiKeyIdsService-key IDs. Personal-key jobs are attributed to the user.
limitInteger from 1 to 100; defaults to 50.
cursorOpaque cursor returned by the previous response.

Repeat an array parameter for multiple values, for example statuses=Running&statuses=Failed. Keep filters unchanged while following a cursor. Jobs are returned newest first, with the job ID breaking creation-time ties.

Summary fields #

Each summary contains id, organizationId, engineId, sourceLocale, trigger, status, createdAt, updatedAt, and createdBy. The status is a tagged object such as { "_tag": "Running" }; a failed status also includes message.

Summaries omit documents and output files. Retrieve a job by id for its document keys, target locales, stage progress, and download URLs.

Store the create response's ID in your own application whenever possible. Listing is useful for investigation and recovery, but the source revision that produced a job belongs in your application's records.