Fleetee API
Connect your tools to Fleetee through the API.
15 articles
Article type
How-to guides (5)
One task, step by step.
- How do I create my API keys?In Settings › API keys, click “Create a key”, name it, choose its access (read-only or read and write), API v3 and the agencies. The key and its secret are shown only once: copy them.VideoScreenshots
- What should I do if an API key is lost or exposed?In Settings › API keys: lost secret, renew it (“Renew the secret” gives your tool 24 hours, “Renew now” cuts the old one at once); lost or exposed key, revoke it (“Revoke”) and create another one.
- How do I notify my tools as soon as a booking is confirmed?In Settings › Webhooks, click “Add a webhook”, enter the address your tool gives you, tick “A rental is confirmed”, then send a test. Fleetee sends each chosen event there, signed, and retries on failure.VideoScreenshots
- How do I limit a key to some agencies or to read-only?In Settings › API keys, click “Edit” on the key’s row: choose “Read-only” as the access and tick the agencies under “Limit to some agencies”. Only what you change is saved, and the restriction applies at once.
- How do I connect Fleetee to Zapier, Make or n8n?In your tool, create a “webhook” trigger to get an address, then paste it into Fleetee’s Settings › Webhooks and tick the events. For the tool to read or write in Fleetee, create a key in Settings › API keys.
Understand (8)
One notion, explained simply.
- What is the Fleetee API for, and what can it do?The Fleetee API is the door through which software reads and writes your data for you: bookings, quotes, customers, vehicles, prices, invoices, payments. It does nothing on its own: a tool, or a developer, calls it with your keys.
- API or booking module: which one do I need?The booking module is a ready-made journey, shown on your Fleetee site or an external site, with no development and no key. The API is for building a custom journey or integration. The two can coexist.
- Do I need to be a developer to use the API?To call the API directly, yes: someone has to write requests. Any language will do: it speaks HTTP and JSON. Without a developer, Zapier, Make or n8n cover simple cases, with Fleetee’s webhooks.
- What is API v3, and should I move off the old API?API v3 is the current version, the one to choose for any new integration. The old API (v1) keeps working unchanged, side by side: a key can open both, and you migrate resource by resource, with no cut-off.
- How do I avoid duplicate customers or bookings through the API?Send an “Idempotency-Key” header on every creation, give your own booking reference, and let the customer rule (same e-mail = same customer) work. Sending again with the same key returns the first answer and creates nothing.
- What should I plan in the API for a network of several agencies?Every booking, price and availability depends on an agency. Plan one key per set of agencies, start from the agency list, do not count on an agency outside the key, and use the attachment request for a customer of another agency.
- Can I trigger or take payments through the API?You can record a payment received elsewhere and create a payment link the customer pays online. The API does not charge a card for you and records no refund. Both calls require an “Idempotency-Key”.
- How much does API access cost?The API has no separate price in Fleetee’s grid. The pricing page lists it under Fleetee Web: “API pour relier votre propre système de réservation” (an API to connect your own booking system). Fleetee Full includes Fleetee Web. Keys are created in Settings › API keys.
Troubleshooting (2)
When something does not work: the causes one by one.
- Why doesn’t an API list contain all my results?A list is cut into pages: 25 results by default, 100 at most. Follow “next_cursor” until it is empty. If results are still missing, check the filters, the key’s agencies, then the call limits (429).
- What do the most common API errors mean?Every API v3 error carries a stable “code” and an HTTP status: 401 the key, 403 rights, 404 the object, 409 a conflict, 422 an invalid field, 429 too many calls. Read the “code”, then give the “request_id” to support if needed.