Ir para o conteúdo
Floweet
Acesso pro

Rate limits

120 requests a minute per organization, 30 for geocoding and routes, 1,000 a day in the sandbox: RateLimit-* headers, the 429 error and Retry-After.

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 · Rate limits
On this page
  1. Headers
  2. Beyond the limit
  3. Other limits
  4. Saving requests

Each organization may send 120 requests a minute per environment (test or live), shared by all its keys. Every response tells you where you stand.

Headers

Response headers
RateLimit-Limit: 120
RateLimit-Remaining: 117
RateLimit-Reset: 42
  • RateLimit-Limit: requests allowed in the one-minute window.
  • RateLimit-Remaining: requests left.
  • RateLimit-Reset: seconds until the next window. Windows are fixed and start at every full minute.

Beyond the limit

The API answers 429 rate_limited with the Retry-After header, in seconds, also given in details.retryAfter. Wait that long, then resume; spread bulk jobs over time rather than running them in parallel.

Response 429
{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please try again in a moment.",
    "details": {
      "retryAfter": 42
    }
  }
}

Other limits

  • Geocoding and routes: 30 requests a minute per environment, on top of the general limit (geocoding and routes).
  • Sandbox: 1,000 requests a day per organization with an fw_test_ key, reset at midnight UTC (429 test_quota_exceeded).
  • A safety net of 600 requests a minute per IP address protects the API before the key is even read.
  • Prospects: 200 at most per organization (422 prospect_limit).
  • Need more? Write to us at contact@floweet.com with your expected volume.

Saving requests

The barometer is recomputed every 30 minutes and station prices follow the official feed: there is no point reading them more often. Ask for pages of 100 items for a full pass, cache the coordinates of an address you already geocoded, and compute a fleet's cost once per data set rather than on every display.