*REST API › Endpoint reference › Operations › Vehicles*

# Create a vehicle

> Registers a vehicle in the fleet.

`collectionId` must be the UUID of an existing collection; tags go by name and one that does not exist is CREATED. Returns the created vehicle.

`POST /api/v1/vehicles` — scope `vehicles:write`

Scope: `vehicles:write` · 120/min · Strict tenancy · Idempotency-Key · If-Match · MCP: `filmo_vehicles_create`

## Authorizations

Bearer API key with the scope below. `vehicles:write`

## Headers

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Idempotency-Key` | string | No | Unique identifier of the request, chosen by the client (a UUID works). Between 1 and 255 characters: an empty header is rejected with 400 `validation_error`, because the client would believe itself protected. Repeating the same key with the SAME body within 24 h returns the stored response without executing again, with the `Idempotent-Replay: true` header. With a DIFFERENT body it returns 422. It is the safe way to retry after a network timeout. |
| `If-Match` | string | No | Optimistic locking: the `ETag` you read from the resource (or `*`). If the resource changed since, the write is rejected with `412 precondition_failed` before doing anything; read it again and retry. Without the header the write always proceeds. |

## Body

Body schema: `VehicleCreateBody`

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | Yes | Vehicle name. |
| `registrationNumber` | string | No | Registration number. |
| `description` | string | No | Vehicle description or notes. |
| `collectionId` | string | No | Collection it belongs to. |
| `tags` | string[] | No | Tags by name; a name that does not exist CREATES the tag. |
| `seats` | integer | No | Number of seats. |

## Request examples

*Create a vehicle*

**cURL**

```bash
curl https://app.filmo.io/api/v1/vehicles \
  --request POST \
  --header "Authorization: Bearer $FILMO_API_KEY" \
  --header "Idempotency-Key: $(uuidgen 2>/dev/null || cat /proc/sys/kernel/random/uuid)" \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "Furgón Sprinter 1",
  "registrationNumber": "1234 KLM",
  "description": "Furgón de carga con portón trasero.",
  "seats": 3,
  "tags": [
    "Flota",
    "Madrid"
  ]
}'
```

**Node.js**

```javascript
fetch('https://app.filmo.io/api/v1/vehicles', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer YOUR_FILMO_API_KEY',
    'Idempotency-Key': crypto.randomUUID(),
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    name: 'Furgón Sprinter 1',
    registrationNumber: '1234 KLM',
    description: 'Furgón de carga con portón trasero.',
    seats: 3,
    tags: ['Flota', 'Madrid']
  })
})
```

**Python**

```python
import uuid
import requests

requests.post("https://app.filmo.io/api/v1/vehicles",
    headers={
      "Authorization": "Bearer YOUR_FILMO_API_KEY",
      "Idempotency-Key": str(uuid.uuid4()),
      "Content-Type": "application/json"
    },
    json={
      "name": "Furgón Sprinter 1",
      "registrationNumber": "1234 KLM",
      "description": "Furgón de carga con portón trasero.",
      "seats": 3,
      "tags": [
        "Flota",
        "Madrid"
      ]
    }
)
```

## Response

Response schema: `VehicleDto`

| Status | Description |
| --- | --- |
| 201 | Successful response. |
| 400 | Invalid request (validation_error): malformed query or body. `errors[]` lists every offending field with its stable code. |
| 401 | Authentication failed (unauthorized, api_key_invalid, api_key_revoked, api_key_expired, api_key_owner_inactive, api_key_owner_not_admin). |
| 403 | Not allowed (insufficient_scope: the API key does not have the required scope, named in `requiredScope`; forbidden: the owner of the key lacks the permission the operation requires). `insufficient_scope` is answered before the request counts against the rate limit, so it carries no `RateLimit-*` headers; `forbidden` does. |
| 404 | Resource not found (not_found): it does not exist or is outside the scope of the API key. |
| 409 | Conflict (conflict): the current state of the resource prevents the operation, a request with that Idempotency-Key is already in progress, or another conditional write (`If-Match`) held the resource for more than five seconds. `errors[0].code` says which: `in_progress` and `lock_timeout` are solved by retrying; `invalid_state` is not, because the state of the resource forbids the operation. |
| 412 | Precondition failed (precondition_failed): the `If-Match` entity tag does not match the current representation. Read the resource again and retry. |
| 422 | Idempotency-Key reused (idempotency_key_reused): the same key was used before with a different body. Change the key. |
| 429 | Rate limit exceeded (rate_limited): retry after `Retry-After` seconds; `RateLimit-*` says which quota ran out. |
| 500 | Internal error (internal_error). |

**201**

| Name | Type | Description |
| --- | --- | --- |
| `data` | object | Fleet vehicle. Does not include operating costs or pricing settings. |
| `data.id` | string | Unique vehicle identifier. |
| `data.name` | string | Vehicle name. |
| `data.status` | string | Operational status: active (available), maintenance (in the workshop) or inactive (out of service). `active`, `maintenance`, `inactive` |
| `data.registrationNumber` | string | Registration number; null if not recorded. |
| `data.seats` | number | Seats, including the driver seat; null if not recorded. |
| `data.payloadKg` | number | Payload in kilograms; null if not recorded. |
| `data.inspectionDate` | string<date-time> | Date of the next technical inspection in ISO 8601 UTC; null if not recorded. |
| `data.collectionId` | string | Identifier of the collection it belongs to; null if it is in none. |
| `data.collectionName` | string | Collection path; null if not applicable. |
| `data.showInPlanner` | boolean | true if it appears in the planner of the account. |
| `data.createdAt` | string<date-time> | Creation date in ISO 8601 UTC; null if not recorded. |
| `data.updatedAt` | string<date-time> | Last modification date in ISO 8601 UTC; null if not recorded. |
| `meta` | object | Additional information about the response. |
| `meta.warnings` | object[] | Lifecycle warnings; present only when the operation is deprecated. |
| `meta.warnings.code` | string | Stable warning code. `deprecated` |
| `meta.warnings.message` | string | For people: what is deprecated, until when, and what to use. |
| `meta.warnings.sunset` | string | Day (YYYY-MM-DD) the operation stops being served. |
| `meta.warnings.replacement` | string | `operationId` of the operation to use instead, or null if there is none. |
| `meta.warnings.link` | string | Where the deprecation is documented (the changelog). |

*Example response · 201*

```json
{
  "data": {
    "id": "vehicle_9f3a2b",
    "name": "Example vehicle",
    "status": "active",
    "registrationNumber": "2026-0001",
    "seats": 1,
    "payloadKg": 1,
    "inspectionDate": "2026-09-01T08:00:00.000Z",
    "collectionId": "collection_9f3a2b",
    "collectionName": "Example collection name",
    "showInPlanner": true,
    "createdAt": "2026-09-01T08:00:00.000Z",
    "updatedAt": "2026-09-01T08:00:00.000Z"
  }
}
```

## Errors

| Status | Codes | Meaning |
| --- | --- | --- |
| 400 | `validation_error` | Malformed query or body. `errors[]` lists every offending field with its stable code. |
| 404 | `not_found` | It does not exist or is outside the scope of the API key. |
| 409 | `conflict` | The current state of the resource prevents the operation, a request with that Idempotency-Key is already in progress, or another conditional write (`If-Match`) held the resource for more than five seconds. `errors[0].code` says which: `in_progress` and `lock_timeout` are solved by retrying; `invalid_state` is not, because the state of the resource forbids the operation. |
| 412 | `precondition_failed` | The `If-Match` entity tag does not match the current representation. Read the resource again and retry. |
| 422 | `idempotency_key_reused` | The same key was used before with a different body. Change the key. |

## Deprecation

This operation is not deprecated. Deprecations are announced with a Deprecation header and a sunset date.

---

Canonical URL: https://docs.filmo.io/rest-api/endpoint-reference/vehicles/create-a-vehicle  
Last updated: 2026-10-25