Flovi B2B Partner API v2

Welcome to the Flovi Partner Reservation API v2 documentation. Flovi is a professional car relocation logistics platform that connects car dealers, leasing companies, rental firms, and garages with a network of vetted drivers to manage vehicle transfers. This API allows B2B partners to seamlessly request real-time pricing quotes, check vehicle delivery schedules, and book relocation jobs—such as home deliveries, inter-branch transfers, service/maintenance transport, or collections of purchased vehicles—with absolute pricing certainty.

Quick Start: How to Create a Reservation

Our B2B API leverages a guaranteed 2-step reservation workflow designed to eliminate pricing friction, handle electric vehicle schedules accurately, and secure slots before confirming. For details on how to authenticate your integration, please refer to the Authentication section.

Authentication

Errors & Validation

The API uses standard HTTP response status codes to indicate the success or failure of requests. When an error occurs, the response body contains a JSON object with structured details to help you diagnose and handle the problem.

Error Response Structure

Every error payload adheres to the following consistent structure:

{
  "statusCode": 400,
  "errorCode": "VALIDATION_ERROR",
  "timestamp": "2026-06-01T15:55:05.123Z",
  "path": "/customers/v2/reservation",
  "correlationId": "8f7d9a1b-1234-5678-abcd-ef0123456789",
  "message": [
    "vehicle.regNo is required for creating a reservation."
  ]
}

Standard Error Codes

Here are the typical machine-readable error codes you should handle in your integration:

Retrieves all active offices (stores) belonging to the authenticated B2B customer (partner). These office IDs (e.g. off_1, off_2) are compatible with the origin/destination officeId fields in quotes and bookings.

Returns a JSON array of office objects with the following fields:

Calculates the binding, guaranteed price and delivery schedule. It verifies if the vehicle is electric (dynamically adding charging breaks if needed) and locks the resulting terms for 15 minutes.

Returns a JSON object with the following fields:

Vaporizes booking friction by turning your guaranteed quoteId into a confirmed job. The details specified in the quote must match the booking parameters.

Returns a JSON object with the following fields:

Allows editing basic reservation details after creation. Details like contact info, recipient contact info, and public notes can be modified. Note that any changes that affect the quote (e.g. locations, schedules) cannot be updated via this endpoint and require a reschedule.

Retrieves all reservations (and their associated drives/trips) belonging to the authenticated B2B customer (partner), sorted by ID in descending order (newest first). Supports cursor-based pagination.

Returns a paginated JSON object containing the reservations:

Retrieves the full details and real-time status of a specific B2B reservation by its unique BigInt ID string.

Returns the full reservation object, identical to the response format of creating a reservation.

Webhooks

Flovi supports webhooks to notify your application in real-time about important events. This allows your system to react to changes automatically without polling the API.

Creating Webhooks

Go to https://customer.flovi.io/organisation/settings, click on Webhooks -> Add. Enter your desired URL and choose the events you want to subscribe to.

The reservation_status_change webhook is triggered whenever the status of a reservation is updated.

Supported Events

This webhook may be triggered for the following events:

• created - A reservation has been created.
• taken – All the drives in reservation has assigned.
• driving – The driver has started driving.
• sealed – The reservation is completed and sealed.
• final_costs - After two weeks of reservation sealing webhook is called to inform total costs. Format is the same as state: sealed, but also includes vehicles information.
• cancelled - The reservation is cancelled.

Webhook Security

To ensure the authenticity of incoming webhook requests, each request includes a signature header that can be used to verify the request was sent by Flovi.

Secret & Signature

When you configure a webhook endpoint, you'll receive a webhook secret. This secret is used to sign each payload using HMAC SHA256.

• Header: x-hub-signature
• Signature Method: HMAC SHA256
• Secret: Provided in the Flovi Dashboard

Calculating Signature

To verify that a webhook request is legitimate, you can compute the HMAC SHA256 signature of the request body using your webhook secret. Here's how to calculate the signature:

1. Obtain the webhook secret
   You can find your secret in the Flovi Dashboard. Keep it safe and never expose it publicly.
2. Extract the request body
   Read the raw request body exactly as it was received, without any modifications.
3. Compute the HMAC SHA256 hash
   Use the webhook secret as the key and the raw request body as the message. The output should be a lowercase hexadecimal string.
4. Compare with the x-hub-signature header
   The signature sent by Flovi is included in the x-hub-signature header. Compare it against your computed hash to confirm authenticity.

Example (in Node.js)

const crypto = require("crypto");

function computeSignature(secret, rawBody) {
  return crypto
    .createHmac("sha256", secret)
    .update(rawBody, "utf8")
    .digest("hex");
}
            

Example Headers

content-length: 16
x-hub-signature: sha256=981c0223305427406b22a4694022562be103419c89e31ee06de2dd9f96f92238
content-type: application/json
user-agent: GuzzleHttp/7
host: webhook.site
            

Model Context Protocol (MCP)

Flovi supports the Model Context Protocol (MCP), allowing you to connect your AI agents, IDEs, and developer assistants (such as Claude Desktop, Cursor, or Windsurf) directly to the Flovi API.

By configuring the Flovi MCP server, your AI assistants can query offices, calculate quotes, and create or list reservations directly through chat interface using natural language.

Client Configuration

To connect your AI assistant, configure the MCP server by adding the following block to your client's configuration file (e.g. claude_desktop_config.json).

Loading...

Loading...

Exposed AI Tools

The Flovi MCP server exposes the following tools directly to the AI model:

• list_offices
  Retrieve the list of active B2B offices / cost centers for the authenticated partner. Use these IDs to specify origin/destination offices and cost centers in quotes and reservations.
• calculate_quote
  Calculate guaranteed price options and alternative schedules for a transport order before booking. Accepts either office IDs or custom address fields.
• create_reservation
  Confirm and book a live, binding transport order using a guaranteed quoteId. Supports an optional externalId to link the reservation to your own system. WARNING: In production, this is immediately binding, dispatches to real drivers, and incurs real costs. Even cancelling the reservation afterwards may incur cancellation fees and costs.
• list_reservations
  Retrieve all reservations and associated drives/trips belonging to the authenticated partner.