Fuel, gas stations, and energy prices

HERE and TomTom commercial fuel price APIs.

HERE and TomTom publish fuel-price API products for station-level fuel price and station search use cases in supported markets. Use only after confirming Thailand coverage, licensing, and redistribution terms.

Commercial Commercial automotive/location APIs for station fuel-price products where market coverage is available Commercial or restricted access; request/contract required On request; vendor-dependent refresh Open source
Runtime role

Catalog only

Access class

Commercial

Access type

Commercial automotive/location APIs for station fuel-price products where market coverage is available

Free status

Commercial or restricted access; request/contract required

Cadence

On request; vendor-dependent refresh

Last verified

2026-05-11

Access class note

Usually needs payment, partner approval, or a commercial agreement before production use.

Used in layers

page reference only

Useful fields

station name, DOEB license/registration number, brand, operator, licensee, address, province/district/subdistrict, lat/lon, fuel products, fuel price, price scope, tax note, effective time, availability status, opening hours, amenities, source ID

Reliability rating

Medium-high for discovery and context; operational reliability depends on endpoint stability.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

How this helps travel recommendations

Turns fuel planning into source-backed road-trip confidence: where stations are, which fuel types they normally support, whether Fuel Now/NGV status suggests a shortage, what the current reference price is, and which source can actually prove the claim.

Endpoint and API notes

HERE and TomTom publish fuel-price API products for station-level fuel price and station search use cases in supported markets. Use only after confirming Thailand coverage, licensing, and redistribution terms.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use EPPO for official price/statistics, PTT OR SOAP and brand pages for operator prices, DOEB for station/LPG/NGV registry, Fuel Now for availability, PTT NGV for gas quantity, and OSM/Google/NOSTRA/Foursquare only for map, hours, amenity, and station-level enrichment.

Recommended refresh

Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.

Travel scoring role

Turns fuel planning into source-backed road-trip confidence: where stations are, which fuel types they normally support, whether Fuel Now/NGV status suggests a shortage, what the current reference price is, and which source can actually prove the claim.

Comparable / backup source

EPPO, PTT OR SOAP, Bangchak, Caltex, Shell, DOEB, Fuel Now, PTT NGV, OSM/Overpass, Google Places fuelOptions, NOSTRA, Foursquare, brand locators, and commercial HERE/TomTom-style fuel APIs after coverage/licensing checks.

Example request

# Verify the documented fuel endpoint before production use.
curl -L "https://docs.here.com/fuel-prices/docs/get-started" -H "Accept: application/json"

Failure modes

  • There is no single all-station all-price Thailand fuel API.
  • EPPO and brand prices are often Bangkok/vicinity or brand-level reference prices, not guaranteed per-station prices.
  • Fuel Now is availability/status, not price.
  • DOEB is a legal registry, not opening hours or live inventory.
  • LPG, NGV, petrol/diesel, aviation fuel, and EV charging use different units and source systems.
  • Google/NOSTRA/Foursquare/HERE/TomTom data can have strict commercial licensing limits.
  • OSM station data is free but incomplete and not authoritative for price or active status.

Last checked and source confidence

Last checked: 2026-05-11.

Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.