Fleetbase · Rate Limits

Fleetbase Rate Limits

The Fleetbase REST API uses standard HTTP semantics and request-side pagination (limit / offset / page) with a default page size of 25 and a maximum of 100 records per list request. On Fleetbase Cloud, consumption is governed primarily by the monthly resource-unit allowance of the plan rather than published per-second request quotas; self-hosted deployments are bounded only by the operator's own infrastructure. Specific numeric request-rate limits are not publicly documented and are not reconciled in this artifact.

Fleetbase Rate Limits is the machine-readable rate-limit profile for Fleetbase on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring records, units, and requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Logistics, Fleet Management, Supply Chain, Last Mile Delivery, and Open Source.

4 Limits Throttle: 429
LogisticsFleet ManagementSupply ChainLast Mile DeliveryOpen SourceRate LimitingQuotasThrottling

Limits

List Page Size request
records
25 default / 100 maximum
Controlled via limit / offset / page query parameters on list endpoints.
Cloud Resource Units account
units
per plan allowance
Fleetbase Cloud meters platform/API activity in resource units; exceeding the monthly allowance incurs $0.75-per-unit overage rather than hard throttling.
Request Rate account
requests
see provider documentation
Numeric per-second/per-minute request throttles are not publicly documented.
Self-Hosted deployment
requests
operator-defined
Self-hosted AGPL deployments are bounded only by the operator's own infrastructure and gateway configuration.

Policies

Pagination
List endpoints paginate via limit / offset / page; default 25, max 100 records.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 / Retry-After responses where returned.
Test Mode
Requests with flb_test_ keys never hit production data and incur no cost, enabling integration testing without consuming live quota.

Sources