Reference · built on requestCommons signalTransit, roads & mobility

Alternative Fuel Stations API

EV charging and alternative fuel station records for the United States and Canada from the DOE Alternative Fuels Data Center.

About

The Alternative Fuels Data Center is run by the National Laboratory of the Rockies for the U.S. Department of Energy. Its station database backs the Alternative Fueling Station Locator and is exposed through the Alternative Fuel Stations API on the NLR Developer Network. Records cover electric vehicle charging, biodiesel, compressed natural gas, ethanol, hydrogen, liquefied natural gas, propane, and renewable diesel stations in the United States and Canada. Each record carries an address, coordinates, access and status codes, owner type, and for EV sites the count of Level 1, Level 2, and DC fast ports, connector types, network, and pricing text. The data is updated on an ongoing basis, and the download page states it may be used for any purpose.

An operator uses it to place charging or fueling stops on a route and to confirm that a planned stop is open to the public before a driver counts on it.

This is a reference listing. It documents what Fibric would read from Alternative Fuel Stations API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • All stations from GET /api/alt-fuel-stations/v1 with the format given as the file extension (json, csv, geojson), filtered by fuel_type, state, zip, country, status, and access
  • Nearest stations from /v1/nearest by latitude and longitude with a radius in miles, default 5.0, up to 500.0 or infinite; results carry distance and distance_km
  • Stations along a route from /v1/nearby-route, given a WKT LINESTRING and a distance in miles, default 5.0, up to 100.0; POST for long routes
  • Per station: id, station_name, fuel_type_code, status_code (E, P, T), access_code, access_detail_code, restricted_access, open_date, expected_date, date_last_confirmed, and updated_at
  • EV fields: ev_level1_evse_num, ev_level2_evse_num, ev_dc_fast_num, ev_connector_types, ev_network, ev_pricing, ev_workplace_charging, funding_sources, and ev_charging_units
  • EV filters: ev_charging_level (1, 2, dc_fast), ev_power_kw_min and ev_power_kw_max, ev_connector_type_operator (OR, AND), and maximum_vehicle_class
  • Charging networks from /v1/electric-networks, unit-level CSV from /v1/ev-charging-units, and the data timestamp from /v1/last-updated

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Plan charging stops on a delivery route

    Route Resequence passes the planned route as a LINESTRING to nearby-route, filters by connector type and DC fast ports, and proposes stops that keep the vehicle inside its range.

    With Route Resequence

  • Confirm a charger is public before a driver arrives

    Charge Readiness re-reads access_code, restricted_access, and status_code for each planned stop and proposes a substitute when a station is private, planned, or temporarily unavailable.

    With Charge Readiness

  • Keep alternative fuel within reach

    Fuel Reserve reads CNG, LNG, propane, and hydrogen stations near a depot, using cng_psi and vehicle class filters, and proposes where a low-tank vehicle should refuel.

    With Fuel Reserve

  • Compare public charging near the yard

    Depot Charging reads EV stations, port counts, and ev_pricing text within a radius of the depot and proposes which vehicles charge off-site when depot ports are full.

    With Depot Charging

Requirements

  • A free API key from the NLR Developer Network signup page
  • Coordinates, a state or ZIP, or a WKT LINESTRING route to scope each query
  • Your fleet's connector types and vehicle class so the filters return stations a driver can use
  • A vehicle location or planned route from another source so a proposal refers to a real trip
Authentication
A free NLR Developer Network API key, passed as the api_key query parameter or the X-Api-Key header.

Limits

  • No more than 1,000 requests per key per hour; the API answers 429 when exceeded and reports X-RateLimit-Limit and X-RateLimit-Remaining
  • DEMO_KEY is capped at 30 requests per IP address per hour and 50 per day
  • The record fields carry no current port-in-use state; status_code says available, planned, or temporarily unavailable at the station level
  • Records cover the United States and Canada only; country defaults to US, so pass country=all or country=CA for Canadian stations

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request Alternative Fuel Stations API ↗

Questions and answers

Which fuels does the API include?
Biodiesel (B20 and above), compressed natural gas, electric vehicle charging, ethanol (E85), hydrogen, liquefied natural gas, propane, and renewable diesel (R20 and above). Filter with fuel_type using the codes BD, CNG, ELEC, E85, HY, LNG, LPG, and RD.
How do I search along a route?
Call /v1/nearby-route with route set to a WKT LINESTRING of coordinates and distance in miles, default 5.0 and at most 100.0. Use POST with form encoding when the route is too long for a URL. Results come back in ascending distance from the route.
What are the terms for using the data?
The AFDC download page states the data are provided by the National Laboratory of the Rockies for the U.S. Department of Energy and may be used for any purpose. The names DOE, NLR, and Alliance may not be used to endorse or promote anything that uses the data.
Ask about Alternative Fuel Stations API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.