DriveCars Partner API

Sell DriveCars car rentals from your own product. Your server calls ours; we are the merchant of record, so we take the payment and carry the supplier relationship.

Everything runs over one REST API at https://{your-base-url}/v1. The base URL is issued to you at onboarding — a sandbox one to integrate against, and a production one at go-live — and it is the only value that changes between the two. Exchange your client credentials for an access token at POST /oauth/token, then send it as a Bearer header on every /v1 call. Tokens last an hour.

The rental flow

Car rentals reserve, then book:

GET  /rentals/availability
POST /rentals/reservations
POST /rentals/reservations/{reference}/book

A reservation is a draft booking. It holds no inventory, and it expires after about 30 minutes — so never promise a customer that a draft will still be bookable later.

Where to go next

• Getting started — from no account to a token to a booking, in the order you will actually do it.
• Authentication — the scopes, and what every auth failure means.
• Car rentals — the product flow in full.
• Errors, Idempotency, Pagination, Versioning — the rules that apply throughout.
• API Reference — every endpoint, every field, with a request builder you can fire against sandbox.
• Webhooks let us tell you when a booking changes instead of you polling for it. Register an endpoint at POST /webhooks.

Need sandbox credentials? Talk to your DriveCars contact.