Essential cookies keep Rooutiq working. Optional analytics requires your permission. Privacy Policy

Developer platform

Connect systems and AI to governed Rooutiq context.

Rooutiq exposes technical integration surfaces around workspace-scoped context, explicit access, source provenance, and read-only contracts. Availability depends on the deployment and the permissions granted to the caller.

Model Context Protocol

Rooutiq MCP server

Add this server URL in your AI client's custom MCP connection settings, then sign in with your Rooutiq account when prompted. Available tools depend on your workspace access.

https://mcp.rooutiq.com/mcp

Your AI provider may have its own plan requirements. For connection help, email support@rooutiq.com. Opening this endpoint as a normal web page does not start a connection.

Open AI connection settings

REST API reference

v1

Optional domain example: Fleet Intelligence API

This optional reference is fleet-specific and does not define Rooutiq as a fleet-only product. Read-only endpoints integrate predictive maintenance data into BI platforms, ERP systems, fleet-management applications, data warehouses and custom operational software.

The fleet reference below is a domain-specific example, not the primary Rooutiq API contract. This reference is intended for technical integration partners. Every example uses a placeholder credential and fictional data — no real workspace, vehicle, VIN or customer information appears anywhere in this document.

Where the API sits

Fleet data sources

  • Telematics
  • Fleet management
  • CMMS / maintenance
  • Procurement

Rooutiq intelligence layer

Evidence, prediction and decision records

Exposed as one stable, read-only, workspace-scoped HTTPS contract.

Enterprise systems

  • BI / data warehouse
  • ERP
  • Fleet applications
  • Custom software

Rooutiq does not require an enterprise to replace its existing operational systems. It provides the intelligence and decision layer those systems consume.

Base URL and environments

The public contract is versioned and expressed against a single Rooutiq host. Paths are stable resources — build against them rather than against any host you may see in a network trace.

Contract base URL
https://api.rooutiq.com/v1

https://api.rooutiq.com is being provisioned

This hostname is the published contract and the target every integration should be written against. It is not yet serving traffic. Until it is, your callable base URL is issued with your credential in Administration → API Access. Only the host changes at cut-over — the version, resource paths, request shape and response bodies documented here do not.

Environments

Production is the only environment currently offered on this API. Credentials carry a rq_live_ prefix to make that explicit. A separate sandbox environment with its own credential prefix and independent limits is not yet available — it is not documented here because it does not exist, and we would rather say so than have you build against something you cannot call.

Authentication

Every request carries a bearer credential in the Authorization header. Generate and manage API credentials from Administration → API Access. Credentials are workspace-scoped, read-only and never transferable between fleets.

Authenticated request
curl "https://api.rooutiq.com/v1/vehicles?limit=100" \
  -H "Authorization: Bearer rq_live_EXAMPLE_KEY"
  • Creation. A workspace administrator generates the credential. The full secret is displayed once, at creation, and is never retrievable afterwards.
  • Rotation. Generating a new credential supersedes the previous one. Deploy the new value before discarding the old.
  • Revocation. A revoked credential stops resolving immediately and every subsequent request returns INVALID_API_KEY.
  • Secret handling. Treat the credential as a server-side secret. Never ship it in frontend code, a mobile binary, a public repository or a support ticket.

Security and tenancy

Workspace access is scoped by membership and permissions; security controls and their verification status are available for review. Infrastructure-provider certifications do not certify Rooutiq. Request deployment-specific evidence, scope, and current control-verification status before relying on any control claim. The properties below describe the supported API controls.

Workspace tenancy isolation
Every response is filtered to the workspace that owns the credential. There is no parameter that widens the scope to another fleet.
Read-only
The API exposes no write, mutation or deletion operation of any kind.
Server-side authorization
The credential is resolved and the plan entitlement checked on the server before any data is read.
Credential scoping
A credential belongs to exactly one workspace and is never transferable between fleets.
Rotation and revocation
Credentials are rotated and revoked from Administration → API Access. A revoked credential stops resolving immediately.
Transport
HTTPS only.
Rate limiting
Enforced per credential; exceeding the limit returns 429 with Retry-After.

Pagination

List resources accept limit (default 100, maximum 500) and offset (default 0). Each response echoes both and includes has_more — advance the offset while it stays true. The fleet summary is a single aggregate and is not paginated.

Paging through vehicles
# page 1
curl "https://api.rooutiq.com/v1/vehicles?limit=250&offset=0" \
  -H "Authorization: Bearer rq_live_EXAMPLE_KEY"

# page 2 — when has_more was true
curl "https://api.rooutiq.com/v1/vehicles?limit=250&offset=250" \
  -H "Authorization: Bearer rq_live_EXAMPLE_KEY"

Rate limits

  • Policy. Requests are limited per credential. Exceeding the limit returns 429 with a Retry-After header stating the wait in seconds.
  • Retry strategy. Honour Retry-After first. Otherwise retry with exponential backoff and jitter; do not retry a 401, 403 or 404, none of which resolve by repetition.
  • Your limit. Limits can differ by plan. The figure that applies to your workspace is shown on your API Access page — no number is quoted here, because a documented limit that does not match your account is worse than none.

API reference

GET?path=/v1/vehicles

List vehicles

Every vehicle in the workspace with its current health score, risk score and odometer reading. Sorted by most recently updated.

Request
curl "https://api.rooutiq.com/v1?path=/v1/vehicles&limit=100&offset=0" \
  -H "Authorization: Bearer rq_live_YOUR_KEY"
FieldTypeDescription
idstringRooutiq record identifier
vehicle_idstringYour own vehicle identifier / unit number
make / model / yearstring / string / numberVehicle identity
statusstringactive, maintenance, inactive
health_scorenumber0–100, higher is healthier
risk_scorenumber0–100, higher means more likely to need service
odometer_kmnumberLatest odometer reading in kilometers
license_platestringPlate as registered
telematics_providerstringSource of this vehicle's data
next_maintenance_datedateNext scheduled service date
Response 200
{
  "vehicles": [
    {
      "id": "veh_EXAMPLE_0001",
      "vehicle_id": "UNIT-114",
      "make": "Freightliner",
      "model": "Cascadia",
      "year": 2021,
      "status": "active",
      "health_score": 78,
      "risk_score": 31,
      "odometer_km": 412880,
      "license_plate": "EXAMPLE-PLATE",
      "telematics_provider": "geotab",
      "next_maintenance_date": "2026-08-19"
    }
  ],
  "count": 1,
  "limit": 100,
  "offset": 0,
  "has_more": false,
  "organization": "Example Logistics"
}
GET?path=/v1/predictions

List maintenance predictions

Predicted failures for the workspace, newest first, including severity, confidence, estimated cost and the recommended action.

Request
curl "https://api.rooutiq.com/v1?path=/v1/predictions&limit=100&offset=0" \
  -H "Authorization: Bearer rq_live_YOUR_KEY"
FieldTypeDescription
idstringPrediction record identifier
vehicle_idstringVehicle the prediction belongs to
prediction_typestringbrake_wear, oil_change, battery, engine_issue, …
severitystringlow, medium, high, critical
confidence_scorenumber0–100 model confidence. A model output on an unvalidated scale, not a measured accuracy rate.
days_until_failurenumberEstimated days until service is needed
predicted_failure_datedateEstimated failure date
estimated_costnumberEstimated repair cost in USD
statusstringactive, acknowledged, scheduled, completed, false_positive
description / recommendationstringPlain-language finding and next step
Response 200
{
  "predictions": [
    {
      "id": "prd_EXAMPLE_0001",
      "vehicle_id": "UNIT-114",
      "prediction_type": "brake_wear",
      "severity": "high",
      "confidence_score": 81,
      "days_until_failure": 12,
      "predicted_failure_date": "2026-08-16",
      "estimated_cost": 640,
      "status": "active",
      "description": "Front brake wear trending past service threshold.",
      "recommendation": "Schedule brake inspection within 2 weeks."
    }
  ],
  "count": 1,
  "limit": 100,
  "offset": 0,
  "has_more": false
}
GET?path=/v1/fleet/summary

Fleet summary

Aggregate fleet state in a single call — intended for BI dashboards and executive reporting. Computed over the most recent 2,000 records per type.

Request
curl "https://api.rooutiq.com/v1?path=/v1/fleet/summary&limit=100&offset=0" \
  -H "Authorization: Bearer rq_live_YOUR_KEY"
FieldTypeDescription
total_vehiclesnumberVehicles in the workspace
avg_health_scorenumberMean health score across the fleet
critical_alertsnumberActive predictions at critical severity
active_predictionsnumberAll predictions still in active status
total_maintenance_costnumberSum of logged maintenance costs in USD
organization / planstringWorkspace name and current plan
Response 200
{
  "total_vehicles": 214,
  "avg_health_score": 82,
  "critical_alerts": 3,
  "active_predictions": 47,
  "total_maintenance_cost": 128400,
  "organization": "Example Logistics",
  "plan": "professional"
}
GET?path=/v1/maintenance/records

List maintenance records

Completed and in-progress service history, newest service date first. This is the data behind ROI and accuracy reporting.

Request
curl "https://api.rooutiq.com/v1?path=/v1/maintenance/records&limit=100&offset=0" \
  -H "Authorization: Bearer rq_live_YOUR_KEY"
FieldTypeDescription
idstringRecord identifier
vehicle_idstringVehicle serviced
service_typestringType of work performed
service_datedateWhen the work was done
costnumberTotal cost in USD
descriptionstringWork performed
statusstringRecord lifecycle status
technician_namestringWho performed the work
next_service_datedateNext service due, if set
Response 200
{
  "records": [
    {
      "id": "mrc_EXAMPLE_0001",
      "vehicle_id": "UNIT-114",
      "service_type": "brake_service",
      "service_date": "2026-07-28",
      "cost": 612,
      "description": "Replaced front pads and rotors.",
      "status": "completed",
      "technician_name": "A. Technician",
      "next_service_date": "2027-01-28"
    }
  ],
  "count": 1,
  "limit": 100,
  "offset": 0,
  "has_more": false
}

Errors

Versioned requests return a structured error carrying a stable code and a request_id. Branch on the code, never on the message — the wording may be improved, the code will not change. Every response, including successful ones, also carries the id in an X-Request-Id header; quote it when contacting support.

Error response
{
  "error": {
    "code": "INVALID_API_KEY",
    "message": "The API credential is invalid or has been revoked.",
    "request_id": "req_EXAMPLE0000000000000000"
  }
}
StatusCodeCause
401MISSING_API_KEYNo credential was supplied, or the Authorization header is malformed.
401INVALID_API_KEYThe API credential is invalid, revoked, or does not resolve to a workspace.
401API_KEY_CONFLICTThe credential resolved ambiguously and was refused. Rotate the key from Administration → API Access.
403PLAN_REQUIREDAPI access requires an active Professional or Enterprise plan, or an active trial.
404UNKNOWN_RESOURCEThe requested resource path is not part of the published contract.
429RATE_LIMITEDToo many requests for this credential. A Retry-After header states how many seconds to wait.
500INTERNAL_ERRORThe request failed inside Rooutiq. Retry with backoff and quote the request_id to support.

Versioning and changes

The version is carried in the path. Within v1 we may add resources and add fields to existing responses; we will not remove a documented field or change its type. Treat unrecognised fields as additive and ignore them.

v1 — current
Versioned resource paths, structured errors with stable codes, and request_id correlation on every response.
Earlier integrations
Unversioned paths and the original flat { "error": "message" } body continue to work unchanged. Nothing needs to be migrated on a deadline; move to v1 when you want the structured errors.

Support and scope

This API is read-only. Write access, webhooks, work-order, procurement and decision-record resources are not part of the contract today, and are handled case by case for enterprise fleets. Email support@rooutiq.com with what you are building — include the request_id for any failing request — and we will tell you directly whether it is supported today.