Driveosplatform catalogue

How another system books rides

For people connecting another system to the platform: what it is for, how access is granted and what a first call looks like.

An API is how another system talks to the platform without a person in between. Example: a hotel system knows a guest arrives at 5 a.m. and books the ride by itself — no phone call, no typing, no waiting for someone to pick up.

ItemValue
Base URLhttps://driveos.eu/api/v1
AuthenticationAPI key in X-API-Key or Authorization: Bearer <key>
FormatJSON, UTF-8; Content-Type: application/json
Rate limit120 requests per minute per key
Paginationpage and pageSize (at most 100, default 25)
Versionv1 in the path; a new version gets a new number, the old one does not change
ContractGET /api/v1/openapi.json (OpenAPI 3.1)

First call

Start with whoami: it returns the key name, the company and the scopes the key holds. If whoami passes, the key is valid and the network path is open.

curl -s https://driveos.eu/api/v1/whoami \
  -H "X-API-Key: $DEMO_TAXI_KEY"
json200 — odgovor
{
  "key": {
    "name": "Rezervacije hotela",
    "scopes": ["read", "rides", "book", "pricing"]
  },
  "company": {
    "slug": "taxi-a",
    "displayName": "DEMO-TAXI",
    "currencyCode": "EUR",
    "countryCode": "HR",
    "timeZone": "Europe/Zagreb"
  }
}

Service catalogue

Before booking, fetch the service types: the serviceTypeId from that response is mandatory in every booking. The same area returns vehicles and drivers if the key holds those scopes.

bash
curl -s https://driveos.eu/api/v1/service-types -H "X-API-Key: $DEMO_TAXI_KEY"
curl -s "https://driveos.eu/api/v1/vehicles?active=true&pageSize=50" -H "X-API-Key: $DEMO_TAXI_KEY"
curl -s "https://driveos.eu/api/v1/drivers?pageSize=50" -H "X-API-Key: $DEMO_TAXI_KEY"
json200 — vrste usluge (skraćeno)
{
  "serviceTypes": [
    {
      "id": "8f1c2a6e-6d4b-4f2a-9d31-2a7c1b6e5f01",
      "code": "STANDARD",
      "name": "Standard",
      "paymentMethods": ["CASH", "CARD"],
      "seatCount": 4,
      "isActive": true
    },
    { "id": "…", "code": "COMFORT", "name": "Comfort", "seatCount": 4, "isActive": true },
    { "id": "…", "code": "START", "name": "Start", "seatCount": 4, "isActive": true }
  ]
}

Pagination and filtering

Every list returns meta with the page count, so a loop does not have to guess. The parameters are the same on all lists: page, pageSize (or limit), plus status, from, to, updatedSince, serviceTypeId, driverId, q and externalId on rides.

jsonmeta u svakom popisu
{
  "rides": [ /* … */ ],
  "meta": { "page": 1, "pageSize": 25, "total": 128, "pages": 6, "hasMore": true }
}
Sync without gapsFor regular sync use updatedSince (ISO 8601): fetch every change since the last successful call, and let the ride.updated webhook tell you when something changes between two cycles.

Times and time zones

All times in responses are ISO 8601 in UTC (2026-11-17T08:12:00.000Z). Dates in filters (from, to for statistics) are the company’s local days in YYYY-MM-DD format and are interpreted in the company time zone (Europe/Zagreb for DEMO-TAXI).

Where to go next