Updated: 2026-11-06
Your systems can read from and write to Driveos: orders, rides, drivers, prices and invoices. Access is per company, with its own key and scopes, and events arrive on your webhook.
The public and the business API cover the same work you do in the company console.
Every company has its own keys. A key carries scopes, is shown only when it is created and can be revoked at any time. Traffic is limited to 120 requests per minute.
You do not have to poll for events: Driveos sends a signed request to your address. Today the event is ride.updated, and every delivery is logged and retried.
The API and webhooks need the addon.api_access module. We enable it per company, and you issue the keys in the company console. Without it the business API returns an error, while the public ride-tracking routes keep working.
The API does not change who is responsible: you remain the carrier and Driveos is the software. Data stays tied to your company and can be exported.
Yes. The API and webhooks need addon.api_access, which we enable per company.
HMAC-SHA256 over the timestamp and the request body; the signature is in the x-whitelabel-signature header.
120 requests per minute.
Currently ride.updated. The list is visible in the console and grows with new features.
Yes. The public channel takes orders per company, and the partner channel has its own token and rules.
In the company console, under API keys. The secret is shown only once.
Half an hour, your zones and your prices. We open a company and show you this part of the system — from the order to the invoice.
We show you the API on your own case — your data and your system.