A Vehicle Operating System with a real API.
Everything the operator UI does, the API does. Typed REST, OpenAPI 3.1, per-event webhooks, and a schema that stays stable across every powertrain.
REST API
Typed REST endpoints for vehicles, drivers, trips, work orders, geofences, incidents and warehouses. Same schema across ICE, hybrid, electric and hydrogen — swap powertrain, keep the integration.
OpenAPI 3.1
Full OpenAPI specification kept in sync with the code. Point Postman, Insomnia or your codegen at it and get typed clients in TypeScript, Python, Go, or Java.
Webhooks
Subscribe to per-event webhooks (trip.completed, incident.raised, work_order.created, charging.session_ended) with HMAC signatures and delivery retries. Never poll.
Auth
OAuth 2.0 client-credentials for machine-to-machine, and short-lived JWTs for user-context calls. Scoped API keys for narrow integrations. Tenant isolation enforced at every layer.
Rate limits
Generous default limits per tenant, published in Retry-After headers. Enterprise plans lift the ceiling. No hidden throttling.
Versioning
API changes ship additively; breaking changes get a new major (v1 → v2) with a twelve-month deprecation window. No surprises the morning after a deploy.
A minimal request
GET the current fleet snapshot — one vehicle, latest signals, powertrain-normalized.
curl -H "Authorization: Bearer $TOKEN" \
https://api.intellitech.cl/v1/vehicles/PU-08
{
"id": "PU-08",
"unit_id": "Hilux Service",
"powertrain": "ice",
"location": { "lat": -33.4520, "lon": -70.6580, "ts": "2026-05-05T14:32:11Z" },
"range": { "type": "fuel_pct", "value": 68 },
"consumption": { "unit": "L/100km", "value": 9.2, "window_km": 100 },
"state": "on_route",
"next_service": { "type": "brake_pads_front", "eta_days": 18, "confidence": 0.86 }
}Get API access.
The OpenAPI spec and a sandbox tenant are available on request. Email contacto@intellitech.cl with your integration scope.