# List the files a VOD job can analyze

Every analyzable container under the Engine's content directory, as the relative paths a job names its file by, newest first. At most 500 entries are listed; truncated: true marks a listing that was cut off, and the newest files are the ones kept. A listing is not a probe: a file here can still turn out to carry no H.264 track, which the job reports when it runs.

Endpoint: GET /vod/files
Version: 2.0.0
Security: engineBasic

## Response 200 fields (application/json):

  - `files` (array, required)
    The analyzable files, newest first.

  - `files.file` (string, required)
    Path relative to the content directory, with forward slashes — post it back verbatim as a job's file.

  - `files.size_bytes` (integer, required)
    File size in bytes.

  - `files.modified_at` (string, required)
    Last modification time, RFC 3339 with a UTC offset.

  - `truncated` (boolean, required)
    True when the listing was cut off at its maximum of 500 entries.

## Response 503 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.