Skip to main content

​
Overview

This release covers the topic of price resolution and changes in the API schema related to prices.

​
Why this was delivered

As more partners and stations were onboarded, more tariffs turned out to depend on session duration or energy consumed rather than being one flat number. A single price field can’t represent a tiered tariff without discarding information, so a resolved, tree-shaped structure replaces it. See Prices Overview for the full explanation of the model.

​
Impact

Integrations that display name of the location using name field from:
  • GET /stations/details/
  • GET /stations/around/
  • GET /users/<str:user_id>/charging-sessions/
  • GET /users/<str:user_id>/charging-sessions/<str:session_id>/
  • PATCH /users/<str:user_id>/charging-sessions/<str:session_id>/
  • POST /users/<str:user_id>/charging/start/

​
Required action

[MIGRATE DEPRECATED FIELD] Updated schema marks older fields as deprecated:
  • time_price and blocking_fee price types
  • gross_price, net_price, user_facing_price and grace_period_minutes from time slots
  • time_cost and blocking_fee_cost from session detail’s cost summary
  • user_facing_session_prices from session detail’s
Integrations using these fields should migrate to the use of the new one. Older ones are still returned but not fully supported, since more platform tariffs require enhanced representation.