Skip to content

Version 1.7.0

This release brings heavy-duty refuelling into the platform from end to end, replaces two overlapping data-quality indicators with one clear completeness measure, and grows the data API with new fields and a sandbox you can try without an account. Accounts, stations, and existing data are unchanged, and current API integrations on version 1 keep working exactly as before.

Heavy-duty 700 bar refuelling, end to end

Stations that serve heavy-duty vehicles at 700 bar can now be represented across the whole platform. The new option appears in the operator portal forms, on the public map and its statistics, and in the data exports. If you operate heavy-duty refuelling, you can now record it accurately and have it shown to the public.

A clearer picture of station completeness

Each station previously carried two overlapping data-quality indicators that were easy to confuse. They are now a single, easy-to-read gradient with four steps, from incomplete through publishable and AFIR compliant to complete. Each step tells you exactly which fields are still missing, so you always know what to fill in next to move your station forward. Staff continue to see the underlying AFIR and overall percentages.

A bigger, easier-to-try data API

The data API gains a new version 1.1 alongside the existing version 1:

  • More AFIR static data: the export now includes the full set of AFIR reporting fields for each station, including region, vehicle categories, vehicle dimension limits, parking spaces, and daily hydrogen capacity. A new endpoint lists the EU vehicle categories so the codes are easy to resolve.
  • A station overview for data senders: organisations that send us availability signals can now ask the API for their own stations, grouped into those that are live on the public map and those still in testing.
  • A no-account sandbox: prospective data users can integrate against realistic sample responses using a single shared sandbox token, with no account and no access to live data, before requesting real credentials.
  • New interactive documentation: the API reference is now an interactive page where you can try requests directly, served entirely from our own address.

Version 1 is now marked as deprecated. It keeps working unchanged and receives no new features, and each version 1 page links to its version 1.1 counterpart so you can upgrade when you are ready.

If you operate, report on, or consume data for stations, see Action Required for what each role needs to do after this release.