Fleetio

What you can build

• Turn a fault into a work order

  A fault_created webhook arrives with the vehicle and code. The operator checks open issues and service history, then proposes an issue and a work order with the right service task for a fleet manager to approve.

  With Vehicle Fault

• Catch a missed inspection

  Inspection schedules show which vehicles are due. When a submitted inspection form fails an item or a schedule lapses, the operator proposes an issue and a vehicle status change.

  With Inspection Gap

• Question an odd fuel entry

  Fuel entries and meter entries arrive per vehicle. When volume or cost falls outside the vehicle's own history, the operator proposes a comment on the entry and a review by the driver's supervisor.

  With Fuel Anomaly

• Have parts ready before the bay opens

  Work order line items name the parts. The operator checks part locations and open purchase orders and proposes a purchase order draft when stock is short.

  With Parts Readiness

Requirements

• A Fleetio account and a user allowed to open Manage API Keys and add a key with a label and API version
• The Account-Token from the bottom of the Manage API Keys page on every request except /accounts
• Webhook endpoints configured under account settings that answer HTTP 200 within 30 seconds
• Your own records for testing: sample data under a trial account is not accessible via the API

Authentication

An API key created under Settings, Manage API Keys, sent as Authorization: Token followed by the key, plus the Account-Token header from the same page; the API version is chosen when the key is created.

Limits

• Rate limits depend on your plan; a 429 response carries Retry-After in seconds
• Cursor pagination returns 50 records by default and at most 100 per page
• Failed webhook deliveries are retried for 24 hours, and a webhook is disabled after 3 consecutive failures
• Webhook event records are kept for 30 days

Questions and answers

How do I authenticate to the Fleetio API?

Create an API key under Settings, Manage API Keys, choosing a label and an API version. Send it as Authorization: Token followed by the key, and add the Account-Token header shown at the bottom of that page. The /accounts endpoint is the only one that does not need Account-Token.

Which events can a webhook subscribe to?

One or all Webhook Events. The schema names events such as vehicle_created, vehicle_updated, issue_created, issue_resolved, fault_created, fault_resolved, work_order_created, work_order_updated, submitted_inspection_form_created, fuel_entry_created, and purchase_order_closed. Each POST is signed with HMAC SHA-256 in the X-Fleetio-Webhook-Signature header.

What are the rate limits?

Fleetio does not publish numbers; it says to consult your plan. When you exceed the limit the API returns 429 Too Many Requests with a Retry-After header giving the seconds to wait, and requests succeed again after that period.