---
title: "Show Background Job Status"
method: GET
path: "/background_job_status/{backgroundJobStatusId}"
tags: ["Background Job Status"]
---

# Show Background Job Status

`GET /background_job_status/{backgroundJobStatusId}`

## Request

- Base URL: `https://api.wistia.com/modern`
- URL: `https://api.wistia.com/modern/background_job_status/{backgroundJobStatusId}`
- Auth: HTTP bearer

Retrieves the status of a background job.

## Requires api token with one of the following permissions
```
Read all data
```

Tokens with the "Act with a team member's permissions" permission
(`all:delegate_to_contact_permissions` scope) can also be used. Requests
made with such a token are authorized using the permissions of the
contact assigned to the token.

An [expiring access token](https://docs.wistia.com/reference/post_expiring-token)
created with the `all:delegate_to_contact_permissions` scope can also be
used when its authorizations cover the record the job acts on: any
permission on that media, folder, channel or webinar suffices, and a job
on the account itself is covered by every token for that account. Jobs on
other records, including bulk operations, are not found.

## Path parameters

- `backgroundJobStatusId` string, required

## Headers

- `X-Wistia-API-Version` string, required

## Response `200`

OK

- object
  - `background_job_status` object, required: A background job keeps track of the progress of an asynchronous task, e.g bulk archiving media, translating media, etc.
    - `id` integer, required: The ID of the background job that's been queued for the request.
    - `hashed_id` string, required: The unguessable hashed ID of the background job. Prefer this over the numeric ID when polling for status.
    - `status` 'queued' | 'started' | 'finished' | 'failed', required: The status of the background job that's been queued for the request.
    - `object` object: Wire view of a bulk operation as it appears inside a background job status poll response. Discriminated by `type`.
      - `type` 'bulk_operation', required: Discriminator identifying the wrapped resource type.
      - `summary` object, required: Aggregate counts for the bulk operation. While the operation is running, `succeeded` and `failed` reflect progress so far.
        - `total` integer, required: The total number of actions in the operation.
        - `succeeded` integer, required: The number of actions that have completed successfully.
        - `failed` integer, required: The number of actions that have failed.
      - `results` object[], required: Per-action results, in submission order. Empty until actions begin completing.
        - `position` integer, required: The zero-based index of the action within the submitted batch.
        - `operation` 'create' | 'update' | 'delete' | 'move' | 'purchase': The operation that was performed. `purchase` appears only for operations submitted through the Create Bulk Purchase endpoint.
        - `resource_type` string: The type of resource the action operated on.
        - `id` string: The hashed ID of the affected record. For successful creates this is the newly created record's ID. Absent when a create fails before a record exists.
        - `status` 'succeeded' | 'failed', required: The outcome of the action.
        - `error` string: The failure reason. Only present for failed actions.

## Other responses

- `401`: Unauthorized, invalid or missing token
- `404`: Resource not found
- `500`: Internal server error

## Changes

- **2026-11-03** `b86cb2a7b420`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/wistia/apis/data-api/changes/background_job_status/:backgroundJobStatusId/get.md)

---

[API](https://skmtc.dev/wistia/apis/data-api.md) - [All operations](https://skmtc.dev/wistia/apis/data-api/llms.txt) - [OpenAPI document](https://skmtc.dev/wistia/apis/data-api/revisions/b86cb2a7b420?raw)