Ir para o conteúdo
Floweet
Acesso profissional

Floweet API documentation

A JSON REST API to connect your tools to Floweet's fuel prices, stations, company directory and simulations: step-by-step guides, every operation in detail, examples in curl, JavaScript and Python.

api.floweet.com/v1 · Contract 1.0.0-beta.1 · Beta

This documentation is written in English and French; it is shown to you in English.

Sections

The Floweet API lets your server read this week's fuel prices and the brand ranking, fuel and EV charging stations, the SIRENE company directory with each company's estimated fleet, price a fleet's fuel and carbon overspend, and work with your organization's prospects and simulations. Built for fuel card issuers, station networks, fleet managers and their software vendors. Every example comes in curl, JavaScript and Python.

At a glance

  • A JSON REST API, at https://api.floweet.com/v1: 21 operations under 10 scopes.
  • One API key per organization, acting for a designated ADMIN member: it sees exactly what that member sees, with the organization's plan (authentication).
  • A sandbox (fw_test_) on the same data, where pitches are written from the template, without AI (sandbox).
  • Web standards: cursor pagination, Idempotency-Key, RateLimit-* headers (120 requests a minute), errors with stable codes.
  • Access on request, opened by our team: contact@floweet.com. The API is in beta.
First call
curl "https://api.floweet.com/v1/barometer?fuel=gazole" \
  -H "Authorization: Bearer $FLOWEET_API_KEY"

Get started

Resources

Protocol

Versions

The reference, served by the API

This documentation and the reference are generated from the same contract the API validates your requests with. The reference remains available alongside:

In preparation

  • Self-service developer spaceComing soon — create, name and revoke your keys, follow your usage, ask for production yourself. Today, our team does it for you, by e-mail.
  • Outgoing webhooksComing soon — be told about a price change or a simulation's progress instead of polling the API.
  • MCP serverComing soon — the same operations, exposed to AI assistants, with the same scopes.
  • Access included in plansComing soon — open the API from your subscription, without asking, with a bundle of calls.