How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HERE Fuel stations API

Search fuel stations

HERE Fuel stations API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Fuel Stations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 6 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://fuel-v2.cc.api.here.com, https://fuel-v2.cit.cc.api.here.com, https://fuel.hereapi.com/v3.

7 operations 6 paths 28 schemas 6 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://account.api.here.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

HERE Fuel stations API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). An API key is passed in the query as apiKey (ApiKey).

  • Bearer — A token obtained from a separate endpoint using client credentials and an OAuth 1.0a HMAC-SHA256 signed request. For more information on how to get a bearer to…
  • ApiKey — A key generated specifically to authenticate API requests. For more information on how to get an API key, see https://developer.here.com/documentation/identity…

Paths & Operations 7

Across 6 paths, the API surfaces 7 operations — 6 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Fuel stations 7

Search fuel stations

GET
/fuel/stations
Fuel stations search
FuelPricesAPIV2FuelStationsSearch 13 params → 200400401403429500502503
GET
/fuel/stations/{id}
Fuel station details
FuelPricesAPIV2FuelStationDetail 2 params → 200400401403404500
GET
/stations
Fuel stations search
FuelPricesAPIV3FuelStationsSearch 9 params → 200400401403429500502503
POST
/stations
Fuel stations along the route search
FuelPricesAPIV3FuelStationsCorridorSearch 8 params body → 200400401403429500502503
GET
/stations/{id}
One fuel station data
FuelPricesAPIV3FuelStationDetail 3 params → 200401403404429500502503
GET
/stations/bulk
Return multiple fuel stations
FuelPricesAPIV3FuelStationBulk 4 params → 200400401403429500502503
GET
/stations/count
Number of fuel stations
FuelPricesAPIV3FuelStationsCount 2 params → 200400401403429500502503

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are FuelStation (15 properties), FuelStation_2 (14 properties), Address (11 properties), FuelPriceType (9 properties). Each schema is shown below with its type and property counts.

TimePeriodType
object
2 properties
AnnualOpeningHoursDetailType
object
3 properties
FuelStationDetailType
object
Other fuel station details - opening hours, accessibility, etc
6 properties
FuelStationsResult
object
2 properties
OpeningHoursDetailsType
object
2 properties
Error
object
2 properties
ContactType
object
Fuel station contacts
4 properties
OperationalStateType
object
An "operational state" for a fuel station refers to its current status, which can be active and selling fuel or closed, and is determined by factors like the a…
5 properties
AddressType
object
Fuel station address
8 properties
PositionType
object
WGS84 format co-ordinates for the fuel station
2 properties
OpeningHoursType
object
2 properties
FuelStation
object
15 properties
HydrogenStatus
string
Status of hydrogen dispensor
AuthError
object
Error object reported in case of authentication or authorization errors.
2 properties
FuelPriceType
object
Information on the prices for fuels at the station.
9 properties
ErrorResponse
object
6 properties 6 required
KeyValueType
object
2 properties
AnnualOpeningHoursDetailType_2
object
3 properties
CorridorSearchRequest
object
Body payload for corridor search
2 properties
FuelStationsResult_2
object
5 properties
OpeningHoursDetailsType_2
object
2 properties
Address
object
11 properties
ContactType_2
object
Fuel station contacts
4 properties
OpeningHoursType_2
object
2 properties
FuelStation_2
object
14 properties
Location
object
Location on the Earth
3 properties 2 required
FuelStationsCount
object
Number of fuel stations response
1 property
FuelPriceType_2
object
Information on the prices for fuels at the station.
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-fuel-stations-api-openapi.yml Raw ↑

Other APIs HERE publishes across the network.

HERE Geocoding and Search API
HERE Autosuggest API
HERE Tour Planning API
HERE Public Transit API
HERE Destination Weather API
HERE Map Tile API
HERE Map Image API
HERE Tracking API
HERE Positioning API
HERE Parking API
HERE Platform Data API
HERE HD Live Map
Where this information came from

This is an independent, third-party profile of HERE Fuel stations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.