> ## Documentation Index
> Fetch the complete documentation index at: https://detrack.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Vehicle checks: Checklists drivers submit for their vehicle

> A vehicle check submission is one completed checklist, such as a start-of-day inspection, with the driver's answers, photos, and signature.

A **vehicle checklist** is a set of questions you set up in the Detrack dashboard, for example a start-of-day inspection. Each time a driver fills one in for their vehicle, Detrack saves a **vehicle check submission**. The API lets you read submissions. Creating, approving, or deleting them happens in the dashboard and the driver app.

## Fields

* `id` (string) — The submission's ID.
* `vehicle_checklist_id`, `vehicle_checklist_name` — Which checklist the driver filled in.
* `trackable_id`, `trackable_name`, `detrack_id` — The vehicle the check is for. `trackable_name` is the vehicle's name when the check was submitted, and doesn't change if you rename the vehicle later.
* `started_at` — When the driver opened the checklist.
* `created_at` — When the driver submitted it.
* `passed_item_count`, `failed_item_count` (integer) — How many pass/fail questions passed and failed.
* `signature_name`, `signature_url` — The driver's signature, if the checklist asked for one.
* `vehicle_checklist_is_approval`, `approval_status`, `approval_user_name`, `approval_user_email`, `approval_date` — Manager approval, for checklists that need it. `approval_status` is `pending` until a manager approves it.
* `items` (array) — One entry per answered question, with `vehicle_checklist_item_name`, `value`, `notes`, and up to four photo links.

## Dates and times

Timestamps such as `started_at` and `created_at` use your organisation's time zone offset, for example `2026-11-03T08:42:18.204+08:00`. The `from` and `to` filters are whole days in that time zone too, so `from=2026-11-03&to=2026-11-03` returns checks submitted between midnight and 23:59 on 3 November, local time.

## Answers

Every `value` is a string:

* **Pass/fail** questions answer `"true"` for pass and `"false"` for fail.
* **Numeric**, **dropdown**, and **text** questions answer with what the driver entered or picked, for example `"48210"`.

## Odometer readings

There is no dedicated odometer field. If your checklist has a question for the odometer, the reading is that question's `value`. Find it by `vehicle_checklist_item_name` (for example `Odometer`), or by `vehicle_checklist_item_id` if you might rename the question.

## Start-of-day and end-of-day checks

A submission doesn't record whether it was a start-of-day or end-of-day check. Use separate checklists for each, and tell them apart by `vehicle_checklist_name` or filter with `checklist_id`.

## Photos and signatures

`photo_1_url` to `photo_4_url` and `signature_url` are temporary download links. They expire about 15 minutes after the response. Download the files you need when you fetch the submission, and don't store the links. Fetch the submission again for fresh links.

## Who can read submissions

The API key's user must be the account owner, or a manager allowed to manage driver checklists, and your account must include vehicle checks. Otherwise both endpoints return `403`. A manager whose access is limited to groups only sees submissions for vehicles in those groups.

Request checks run before the permission check. An invalid `from`, `to`, or filter returns `422`, and an unknown ID returns `404`, even for a key that would get `403`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.