---
title: "Get Job Status By Game"
method: GET
path: "/api/v1/jobs/by-game/{game_id}/status"
tags: ["Jobs"]
---

# Get Job Status By Game

`GET /api/v1/jobs/by-game/{game_id}/status`

Get job status by game_id instead of job_id.

The returned `state` is one of:
  - "processing": the video is uploaded and still being processed or reviewed
  - "completed": processing finished — stats are available, or there were no clips
  - "Video can not processed by Mux": the source video could not be processed
  - "Jersey Color Mismatch": the home and away jersey colors could not be told apart
  - "Visible Issue": visible quality issue found during QC
  - "cancelled": the job was cancelled by the client

`processing_started_at` is the worker start time in UTC (+00:00).

## Path parameters

- `game_id` string, required

## Headers

- `x-api-key` string, nullable
- `League` string, nullable

## Response `200`

Successful Response

- JobStatusResponse
  - `job_id` string, required
  - `state` string, required
  - `start_of_play` string — Actual game start time from dms_main.videos.actual_game_start_time formatted as a video timestamp; empty until it is available.
  - `completed_at` string, nullable — Final worker-start-to-status-complete duration formatted as hh:mm:ss; null until processing is complete.
  - `processing_started_at` string, nullable — UTC (+00:00) timestamp when the worker started processing; null until processing has started.
  - `video_quality` object, nullable — Objective video-quality measurements (resolution and frame_rate) with per-component 0-1 scores. Unknown metadata is represented by null component scores. No grade or show/hide decision is implied.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/preciser/apis/preciser-data-management-api.md) · [All operations](https://skmtc.net/preciser/apis/preciser-data-management-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/preciser/preciser-data-management-api/revisions/16e2b6a1c2bb/schema)