Station pricing

Charging prices can be shown at two levels: directly on a map through the tile service, or in full detail through a connector’s pricing.

Tile service

The tile service supports pricing both as filters and as selectors.

• As a filter, pass minimum_energy_price and maximum_energy_price, along with currency to convert the range to the correct currency, to dynamically include or exclude stations whose price falls within that range.
• As a selector, request connector_minimum_energy_price, connector_maximum_energy_price, price_vat, price_valid_until, price_original_currency and price_conversion_rate to show price details. They are returned in the station feature properties (properties.count == 1). The price is always the station price, and you can use price_original_currency and price_conversion_rate to adjust for your own conversion.

Station pricing

Where pricing details come from depends on the station database behind a station.

• If Ecomovement is used, pricing can be found on the pricing object of a station’s connectors, at evses[].connectors[].prices.
• For any other station database, use the dedicated tariffList and tariff queries instead.

A connector can have several price elements active at different times. Work through them in order to render the correct price.

1. Find the active price elementEach price element has restrictions, such as day_of_week, start_time/end_time, or minimum and maximum kWh, power, or duration. Use these to determine which price element applies right now.
2. Display all price componentsA price element can combine several components at once. An energy component gives you the price per kWh. A time component gives you the price per interval, billed in blocks defined by its step_size. For example, a step_size of 300 on a time component bills in blocks of 5 minutes. A flat component adds a fixed amount to the session, independent of energy used or time spent.
3. Account for the overstay feeA parking_time component charges an idle fee for staying connected after charging has finished, since nobody else can use the connector in the meantime. It applies once the connector’s overstay restrictions, such as overstay_time or overstay_battery_percentage, are met.

Each connector can have its own price, and prices can be changed dynamically by the operator at any time.

Rely on last_updated

Since prices can change at any time, always check a price object’s last_updated field before caching or reusing a price, rather than assuming it stays valid.

Thank you for your feedback.

Was this content helpful?