# The job's stored detections, one page at a time

Every response the analysis service returned for the job, as the job stored it — media-time stamped and unfiltered by any listener's gating — verbatim rows, never reshaped. A job still running serves what it has answered so far. ?from_ms&to_ms narrow the page to a half-open stretch of the source. 404 when the job is unknown, when it was submitted with store_results: false, or when it has not stored a row yet; the detail says which.

Endpoint: GET /vod/jobs/{jobId}/results
Version: 2.0.0
Security: engineBasic

## Path parameters:

  - `jobId` (string, required)
    A VOD job's id, as createVodJob answered it.

## Query parameters:

  - `offset` (integer)
    Rows to skip; below zero clamps to zero.

  - `limit` (integer)
    Page size, clamped to [1, 1000].

  - `from_ms` (integer)
    Only rows whose window starts at or after this media time.

  - `to_ms` (integer)
    Only rows whose window starts before this media time.

## Response 200 fields (application/json):

  - `job_id` (string, required)
    The job these results belong to.

  - `offset` (integer, required)
    How many rows were skipped before this page.

  - `limit` (integer, required)
    The page size requested.

  - `count` (integer, required)
    Rows in this page.

  - `total` (integer, required)
    Rows matching the filters, across every page.

  - `results` (array, required)
    The stored rows, verbatim — each the analysis service's own response document.

## Response 400 fields (application/problem+json):

  - `type` (string)
    URI identifying the problem type.

  - `title` (string, required)
    Short, human-readable summary of the problem type.

  - `status` (integer, required)
    The HTTP status code, repeated from the response line.

  - `detail` (string)
    Human-readable explanation specific to this occurrence.

  - `instance` (string)
    URI identifying this specific occurrence of the problem.

## Response 404 fields (application/problem+json):

  - `type` (string)
    URI identifying the problem type.

  - `title` (string, required)
    Short, human-readable summary of the problem type.

  - `status` (integer, required)
    The HTTP status code, repeated from the response line.

  - `detail` (string)
    Human-readable explanation specific to this occurrence.

  - `instance` (string)
    URI identifying this specific occurrence of the problem.

## Response default fields (application/problem+json):

  - `type` (string)
    URI identifying the problem type.

  - `title` (string, required)
    Short, human-readable summary of the problem type.

  - `status` (integer, required)
    The HTTP status code, repeated from the response line.

  - `detail` (string)
    Human-readable explanation specific to this occurrence.

  - `instance` (string)
    URI identifying this specific occurrence of the problem.