tounify | Europe's Comprehensive Electricity Prices API

Explain Country Pricing

Use when the user asks how electricity is priced in a specific European country, or WHY the Tounify API needs a particular value there — "why does Germany need a grid tariff", "do I need a postal code for Dutch customers", "why is Great Britain different", "who sets the network charges in Austria", "when does the night rate start", "why can't we just scrape this ourselves". Returns how that market stacks its price layers (supply, network, taxes and levies), who sets each one, and which request p

Explain Api Concept

Use for "what does X mean" questions about the Tounify API itself and about buying it — parameters (version, sector, resolution, historic_days, include, postal_code), response shape (how to sum components, units, net of VAT, the next polling timestamp), authentication, rate limits, pricing plans, the free tier, data privacy, and datasets. Also the v3 vocabulary: which API versions exist and what each is for, what a registered connection is and what it may hold, the charges that are not per-kWh r

Lint Dayahead Request

Use BEFORE the user sends a day-ahead or connection price request, when they describe what they are about to call and want to know whether it is right — "will this give me the full price", "is it OK to omit the grid tariff", "can I ask for 30 days of history", "can I pass resolution=300", "do I need the postal code", "will this cover the capacity charge on a commercial connection". Predicts the silent wrong answers this API is prone to: a request that returns HTTP 200 with a materially low price

Diagnose Response

Use when the user has ALREADY called the TOUNIFY API and does not understand what came back — any 400/401/403/429 from Tounify, or a Tounify price that looks wrong. Handles "why is Tounify returning 400 unknown tariff id", "my 404 check never fires against Tounify", "we are on a paid Tounify plan but I see 429", "what is this testingLimit block", "my German price from Tounify looks 40% low", "the price array is empty", "my GB price is negative", "my electricity prices look ten times too high", "

Check Coverage

Use when the user asks WHETHER Tounify has data for something, rather than how it works — "which countries do you cover", "do you have feed-in tariffs for the Netherlands", "can I get Polish grid fees", "how many Spanish suppliers do you have", "is Denmark supported". Returns live counts of companies, tariffs and postal codes by country and sector, and states plainly where a layer is unavailable. Do NOT use for: how a market prices electricity (use explain_country_pricing); or what a plan costs

Explain Connection Properties

Use when the user asks WHICH properties of a connection they should send for a country, or what values one takes there — "what do I need to send for a Czech connection", "does Germany use contracted kW", "what connection classes does Estonia have", "which fields matter in France". Returns the properties worth sending in that market, each with what it means there, the unit it is in, and the values it takes where the market publishes a set. A property missing from the answer is one there is no rea

Build Integration Recipe

Use when the user wants to WIRE UP the Tounify API and needs the call sequence — "how do I get German day-ahead prices", "show me the calls", "where do I start", "what is the minimum set of requests for a smart charging app", "I am building a home battery controller", "how do I price a commercial connection", "how do I register a connection". Returns the ordered REST calls with placeholders, the polling contract, and what to assert on, shaped for the country and use case. Do NOT use for: checkin

Estimate Usage

Sizes a TOUNIFY subscription. Use only when the user is asking how much their own Tounify usage will cost, or how many Tounify API calls their design will make — "we have 5,000 heat pumps polling Tounify for prices, which plan do we need", "how many Tounify calls a month is this", "what Tounify volume should we budget for", "how many calls for 800 registered connections". Converts a described electricity-pricing integration into a monthly call estimate, a recommended Tounify plan and the overage

Generate Integration Test

Use when the user wants their Tounify integration to KEEP working — "how do I stop this breaking silently", "what should I assert in CI", "write me a test for this", "how do I catch it if the data changes". Emits a test file pinning the invariants that matter for that market: every layer you asked for present on the point, a grid component present where the market is unbundled, and the tariff ids still resolving and still available. On v3 it also pins that every non-kWh charge on a connection re