Skip to main content
Documentation

Vehicles

vehicles.list

List the vehicles in a customer's garage, or across the shop
Read-onlyRead budget

REST

Shipping
POST /api/v1/vehicles/list

MCP tool

Live
vehicles.list

Exposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Vehicles domain.

Operating contract

With customer_id set this is that customer's garage, newest car first. Without it, every vehicle the shop has on file.

Each result's id is the vehicle_id that vehicles.get, vehicles.update, jobs.list and quotes.list take. Each result's customer_id is the customer_id that customers.get takes.

TRUNCATION: total is the exact number of vehicles matching and omitted is how many are NOT in this response. A garage is usually one or two cars and a whole shop is thousands, so check omitted before answering a question about the shop rather than about one customer — when it is not 0, call again with offset set to next_offset.

Who may call it

Permission
customers.accessThe caller must hold Customers at the ACT level. A read-only dashboard grant on the same section is refused.
Plan
Every planNo plan gate. Available on every Service VIN plan.
Retries
naturalNaturally idempotent — running it twice leaves the same world as running it once. A retrying integration needs no key.
Rate class
readCounted against the read budget — the widest of the four.

Partial answers

omitted is how many matching records are not in the response, and 0 is a real answer meaning you have all of them. Continue with next_offset.

Do not summarise from a truncated response

When `omitted` is not 0 there are more vehicles. Call again with `offset` set to `next_offset`, or narrow with `customer_id`.

Input

FieldTypeDescription
customer_idstringuuid

Only this customer's cars, as returned by customers.list or customers.find_by_contact. Omit for the whole shop.

limitinteger1–100

How many vehicles to return, 1-100. Defaults to 25.

Default: 25
offsetintegermin 0

How many to skip. Pass the previous response's next_offset to continue.

Default: 0

Output

FieldTypeDescription
itemsobject[]

items[].idstring

items[].customer_idstring

items[].labelstring | null

items[].yearnumber | null

items[].makestring | null

items[].modelstring | null

items[].trimstring | null

items[].colorstring | null

items[].vinstring | null

items[].license_platestring | null

items[].mileagenumber | null

items[].vehicle_typestring

items[].created_atstring

totalnumber

omittednumber

next_offsetnumber | null

Examples

Built from this capability's own schema — required fields and the ones carrying a default, and nothing invented. Paste one and it validates.

curl
export SERVICEVIN_API_KEY=svk_live_…

curl -X POST https://www.servicevin.com/api/v1/vehicles/list \
  -H "Authorization: Bearer $SERVICEVIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":25,"offset":0}'

TypeScript (fetch)
const res = await fetch("https://www.servicevin.com/api/v1/vehicles/list", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "limit": 25,
    "offset": 0
  }),
});

// Success and failure are both envelopes. Switch on error.code, never
// on error.message — the codes are stable, the messages are for people.
const payload = await res.json();
if (!res.ok) throw new Error(payload.error.code);
const data = payload.data;

Python (requests)
import os, requests

res = requests.post(
    "https://www.servicevin.com/api/v1/vehicles/list",
    headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
    json={
    "limit": 25,
    "offset": 0
},
    timeout=30,
)
payload = res.json()
if not res.ok:
    raise RuntimeError(payload["error"]["code"])
data = payload["data"]

MCP tools/call — https://www.servicevin.com/api/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "vehicles.list",
    "arguments": {
      "limit": 25,
      "offset": 0
    }
  }
}

Refusals

The four gates run in this order on every surface, and the order is not arbitrary — see Authentication.

StatusCodeWhen
404not_foundThe id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both.
403forbiddenThis login does not hold customers.access.
422validation_errorAn argument was wrong. The message names the field.
429rate_limitedToo many read calls. Back off and retry.
500internal_errorSomething failed on our side. Nothing was changed.