Tariff Selection Workflow
Find Organizations
Use the
/organizations/ endpoint to identify which organizations serve a specific location.Select Organization
End users typically need to select which retailer they use (in liberalized markets where choice exists).
Tariff Characteristics
Chosen vs. Imposed
- Chosen tariffs: Selected by end users (typically retailer tariffs)
- Imposed tariffs: Automatically applied based on location (typically DSO tariffs, taxes, and fees)
Multiple Tariffs
End users typically have:
- One tariff from each relevant retailer
- One tariff from their local DSO
- Multiple applicable tariffs from tax authorities
Pricing Models
Tariffs may use different pricing structures:
- Fixed: Consistent prices regardless of time
- Variable: Prices that change based on predefined schedules
- Spot-based: Prices that follow wholesale market prices
- Capacity-based: Prices based on connection capacity or maximum usage
Time Validity
Tariffs have validity periods:
- Start dates when they become active
- Optional end dates when they expire
- Some tariffs may be superseded by newer versions
valid_at parameter to find tariffs active at a specific time.Retrieving and Filtering Tariffs
The tariffs endpoint requires at minimum a country code and either an organization ID or main tariff ID. You can also filter by location and consumer type to find tariffs applicable to specific users.Basic Retrieval
Location-Based Filtering
Filter tariffs by address to find only those applicable to a specific location:Consumer Type Filtering
Filter by the consumer’slocal_consumer_type or consumer_type to ensure the tariff is applicable:
/local-consumer-types/ endpoint. The local_consumer_types field is also included in tariff responses for building selection UIs.
Example (truncated):
Tariff Properties
Tariffs often have variations based on different criteria, such as contract type (dynamic/variable, fixed, time-of-use based, etc.), housing type (appartment, house, industrial, etc.), the contracted capacity (fuse band/level), amongst others. To help you provide filtering options for your end-users during their tariff selection process, we’ve tagged those astariff properties.
Example of how properties can be linked to tariffs:
Get all Tariff Properties for an organization
Include theinclude_tariff_properties=true parameter to get structured property information:
Example Tariff Properties
Contract Type
Contract Type
Different pricing models offered by retailers:
- Fixed price contracts
- Variable price contracts
- Spot-based/hourly pricing
Housing Type
Housing Type
Tariffs may vary based on property type:
- Apartment
- Villa/house
- Vacation home/cabin
- Commercial property
Fuse Level
Fuse Level
DSO tariffs often vary based on connection capacity:
- 16A
- 20A
- 25A
- 35A
- etc.
Consumption Profile
Consumption Profile
Some tariffs are designed for specific usage patterns:
- Low consumption
- Standard consumption
- High consumption
- EV charging
Tariff Response Structure
The API response structure varies depending on which parameters you include:include_tariff_properties=true: Returnstariff_propertiessection, i.e. the list of all tariff properties returned in the responseinclude_main_tariffs=true: Returnsmain_tariffssection, i.e. the list of all main tariffs returned in the response
Using Tariff IDs
Once you’ve identified the correct tariffs, use their IDs with other endpoints:Current Prices
Get real-time pricing with the
/live/ endpointCalculate Costs
Calculate costs for specific consumption with the
/calculate/ endpointAdvanced Calculations
Enhanced Tariff Details
The enhanced tariff retrieve endpoint returns detailed information about each tariff component, including:- Component structure: Types (KWH, DEMAND, FIXED, TAX, etc.), units, and validity periods
- Calculation requirements: Input specifications needed for advanced pricing calculations
- Time-of-use details: TOU levels and their specific time periods
- Property dependencies: Required tariff properties for accurate pricing
Integration with Advanced Calculations
Some data from thecalculation_requirements section is expected as inputs for the /calculate-advanced endpoint:
Getting Started with Advanced Features
Need More Information? For detailed documentation about the
/calculate-advanced endpoint and how to integrate with the calculation_requirements data, please contact our support team for a demo and access to specific integration documentation.This feature is currently in beta and requires specialized guidance for implementation.
