*REST API › Endpoint reference › Operations › Vehicles*

# Check fleet availability

> Returns, for each vehicle (the whole fleet, or the ones selected by `vehicleIds`, `tags`, `collectionId` or `search`), whether it has commitments overlapping the queried window and which ones, typed.

Same response shape as staff availability. A requested identifier that does not exist comes back as a per-item `error`. Idempotent query (POST because of the structured body). Shares the availability quota of 30 req/min.

`POST /api/v1/vehicles/availability` — scope `vehicles:read`

Scope: `vehicles:read` · 120/min · +30/min availability · Strict tenancy · MCP: `filmo_vehicles_availability_check`

## Authorizations

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

## Body

Body schema: `VehicleAvailabilityBody`

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `startDate` | string<date-time> | Yes | Start of the window to check (ISO 8601 with offset). |
| `endDate` | string<date-time> | Yes | End of the window to check (ISO 8601 with offset); must be later than startDate. |
| `tags` | string[] | No | Only resources carrying ALL these tag identifiers. |
| `collectionId` | string | No | Only resources in this collection. |
| `search` | string | No | Free-text search on the name. |
| `vehicleIds` | string[] | No | Restrict the answer to these vehicles (1-100). An identifier that does not exist comes back as a per-item error. |

## Request examples

*Check fleet availability*

**cURL**

```bash
curl https://app.filmo.io/api/v1/vehicles/availability \
  --request POST \
  --header "Authorization: Bearer $FILMO_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "startDate": "2026-09-01T08:00:00Z",
  "endDate": "2026-09-03T20:00:00Z",
  "tags": [
    "tag_furgonetas"
  ]
}'
```

**Node.js**

```javascript
fetch('https://app.filmo.io/api/v1/vehicles/availability', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer YOUR_FILMO_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    startDate: '2026-09-01T08:00:00Z',
    endDate: '2026-09-03T20:00:00Z',
    tags: ['tag_furgonetas']
  })
})
```

**Python**

```python
import requests

requests.post(
    "https://app.filmo.io/api/v1/vehicles/availability",
    headers={
      "Authorization": "Bearer YOUR_FILMO_API_KEY",
      "Content-Type": "application/json"
    },
    json={
      "startDate": "2026-09-01T08:00:00Z",
      "endDate": "2026-09-03T20:00:00Z",
      "tags": [
        "tag_furgonetas"
      ]
    }
)
```

## Response

Response schema: `ResourceAvailabilityEntryDto`

| Status | Description |
| --- | --- |
| 200 | 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. |
| 429 | Rate limit exceeded (rate_limited): retry after `Retry-After` seconds; `RateLimit-*` says which quota ran out. |
| 500 | Internal error (internal_error). |

**200**

| Name | Type | Description |
| --- | --- | --- |
| `data` | object[] |  |
| `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 · 200*

```json
{
  "data": [
    {
      "resourceId": "resource_9f3a2b",
      "name": "Example resource availability entry",
      "available": true,
      "commitments": [
        {
          "kind": "order",
          "orderId": "order_9f3a2b",
          "orderNumber": "2026-0001",
          "label": "Main",
          "startDate": "2026-09-01T08:00:00.000Z",
          "endDate": "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. |

## 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/check-fleet-availability  
Last updated: 2026-10-25