API documentation
Current observations
Access covers approved markets and current observations only.
Fuel PriceHubAPI documentation
Current observations
Access covers approved markets and current observations only. History and custom analytics are available by separate agreement.
AuthenticationEvery commercial pull uses a customer API key tied to an organization and subscription.
QuotaSuccessful billable data responses count against the included monthly request package.
ProtectionUnavailable coverage, invalid parameters, and unavailable history should fail before billing.
Supported pull patterns
Supported pull patterns
Access covers approved markets and current observations only.
How a request is made
How a request is made
Access covers approved markets and current observations only.
1Access covers approved markets and current observations only.
2Only successful data responses count toward quota or overage.
Billing and quota safety
Billing and quota safety
The intended billing rule is simple: customers should pay for successful data access, not for mistakes, unavailable markets, or unsupported history windows.
Counts toward quota
- Authenticated request returns current station data.
Does not count
- Missing or invalid API key.
- Invalid parameters or unsupported filters.
- Country, city, station, brand, or history window is unavailable.
- Validated request returns no supported data for the requested scope.
- Server-side failure before a usable data response is delivered.
How request metering is enforced
How request metering is enforced
Every commercial request is validated against your API key and organization entitlements, checked against your plan's per-minute rate limit and monthly included requests, and reported to Stripe automatically once you exceed your included quota on a plan with overage enabled.
API keys tied to organization entitlementsPer-minute rate limit enforced per keyMonthly request counters shared across an organization's keysOverage usage reported to Stripe once included quota is exceeded