- Getting started
- Trip updates
Between the Karhoo Platform and DMS's are two distinct types of API endpoints:
- Karhoo endpoints
These are hosted by Karhoo and used by DMS's to push asynchronous updates to Karhoo
- DMS endpoints
These are hosted by the Supply Partner for Karhoo to use to request vehicle availability, quotes and bookings.
Authentication is handled differently for these two classes of endpoints
The Karhoo Supply API is authenticated using the same mechanism as all Karhoo Platform APIs. See How to authenticate for details.
For DMS endpoints Karhoo signs messages using a HMAC. The HMAC signature digest is computed on the payload content using the supplied secret key. This SHA256 hash is sent as lowercase hexits in the
x-karhoo-request-signature header and should be used to validate all requests from Karhoo.
Contact the Karhoo team for help with the above.
Availability and ETA are optional
These are only used when ETA is not included in your Quotes endpoint implementation and you would like to offer On Demand ASAP bookings.
Receive New Trips
DMS hosted API endpoint for receiving Karhoo trip bookings
Provide Trip Details
DMS Hosted endpoint to respond to Karhoo Trip Detail requests
DMS Hosted endpoint to respond to Karhoo Trip Cancellation requests
DMS hosted API endpoint for responding to quote requests
DMS hosted API endpoint for responding to ETA requests
Karhoo Availability Request to DMS
Our Supply API provides an option for our supply partners to push Trip Updates to us directly instead of us requesting this data from their DMS API. This is optional but highly recommended to implement to reduce our polling rate and burden it may cause for your API.
We've made the swagger spec available here which that defines our hosted endpoints as well as what we expect our Supply Partners to implement as webhooks.
We encourage you to use this to autogenerate as much boilerplate as is useful to reduce the workload of writing the integration.
Updated 11 months ago