ITex Services s.r.o.

[ ITexSpot API ]

Czech spot electricity price forecast API

A 7-day outlook of the electricity price in the Czech Republic for Loxone, Home Assistant, evcc, Node-RED or your own script. One address, short responses.

Beta · free · read-only key

Czech bidding zone (CZ) only — prices in CZK, Czech distribution tariffs.

Overview

A complete description of all endpoints and fields is in the API reference (OpenAPI 3.1 specification), the version history in the changelog.

The API returns the published day-ahead market prices for today and tomorrow, followed by our hourly forecast for the rest of the week with an uncertainty band (p10–p90). On top of that it gives the level of each hour (cheap, normal, expensive), the cheapest and most expensive windows, the probability of a negative price and an answer to the question “charge now, or wait?”.

The base URL is https://api.itexservices.cz/v1. Prices are in CZK/kWh, times are ISO 8601 with the Prague offset (2026-11-18T12:00:00+01:00). Field names are Czech without diacritics — they are part of the contract and are explained below and in the reference. The key is read-only and free during the beta — create it in the ITexLink app (My account), or request one using the form on the ITexSpot page (form in Czech).

The data changes three times a day: in the morning around 6:30, after tomorrow’s prices are published around 13:45 and after the main forecast run around 14:35 (Prague time). Every response carries dalsi_aktualizace (next update) — polling more often brings nothing new.

Authentication

The key starts with its_ and has 40 characters. We recommend the key in the path — it works in Loxone, Home Assistant, evcc, Node-RED and scripts, and the response goes through our cache: it is faster and a repeated request does not have to reach the computation.

MethodExampleWhen
Key in the path (recommended)https://api.itexservices.cz/v1/k/<klic>/ted.jsonWherever you can enter a URL
Bearer headerAuthorization: Bearer <klic>Alternative for your own code
Basic Authhttps://<klic>@api.itexservices.cz/v1/…Fallback alternative

The Authorization header (Bearer and Basic Auth) works, but such a response is never stored in the cache — every request then goes all the way to the computation, is slower and uses up more of your limit. With Basic Auth the key can be the user name or the password. The key is read-only; if a URL containing it shows up in a history or in logs, revoke the key and create a new one.

Endpoints

AddressReturnsParameters
vyhled.json7-day series: published prices, then the forecast with its band.krok=60|15, hodin=1–200, strategie
ted.jsonPrice now, level, the nearest cheap and expensive 3-hour window, negative-price risk, “wait”, daily signals.n=1–24, strategie
okna.jsonThe cheapest and most expensive non-overlapping windows of a given length.delka=1–12, pocet=1–5, do=ISO, strategie
loxone.txtSame as ted.json as name=value lines + prices for 48 h and 24 inputs for Spot Price Optimizer.n, strategie
evcc.jsonstart/end/value array for a custom tariff in evcc.strategie
schedule.jsonConsumption schedule: the N cheapest hours a day, or target charging.hodin, pod, kwh+kw+do+ucinnost
export.jsonWhen to limit grid export based on the feed-in price.poplatek, prah
baterie.jsonRecommended hourly battery plan (recommendation only).kapacita, vykon, soc, soc_min, soc_max, soc_konec, ucinnost, opotrebeni, hodin
stav.jsonNo key: time of the last release and age of the data.—

strategie (strategy) selects which forecast value you treat as the “price”: p50 (default, median), p10 (optimistically low) or p90 (cautiously high). Published hours are not affected. An unknown parameter or a value out of range returns 422.

Final price. When the key has a tariff stored (supplier margin, distribution high/low tariff and high-tariff hours, fees, VAT, feed-in fee), responses additionally carry koncova (final price) and vykup (feed-in price), and the “price” field in the text outputs and in evcc is the final price. The tariff is set on the key, not in the URL. Tariffs follow the Czech distribution system (high/low tariff).

Preset supplier tariffs. For a key you can pick a Czech supplier and product (Delta Green — Delta SPOT (odběr a výkup); Delta Green — Delta FLEX (odběr a výkup); ČEZ Prodej — Elektřina SPOT; Centropol — Spotově bez závazku); the choice fills in the margin and the feed-in fee. You still enter distribution (high/low tariff and high-tariff hours) and fees yourself according to your rate. Supplier prices change — we last checked the presets on their websites on 17 November 2026; compare them with your contract before saving.

What the fields mean

One slot from vyhled.json (forecast, key with a tariff)
{
  "od": "2026-11-21T12:00:00+01:00", "do": "2026-11-21T13:00:00+01:00",
  "zdroj": "predpoved",
  "spot": 1.95, "p10": 1.1, "p50": 1.95, "p90": 2.9,
  "koncova": 3.57, "koncova_p10": 2.54, "koncova_p90": 4.72,
  "vykup": 1.45, "p_vykup_zaporny": 0.1,
  "uroven": "levna", "poradi_dne": 1, "p_zaporna": 0.1
}
  • zdroj (source) — trh = published day-ahead market price, predpoved = our forecast.
  • p10, p90 — the forecast uncertainty band. The wider it is, the less certain the outlook.
  • uroven (level) — levna (cheap: the cheapest third of the day’s hours), bezna (normal), draha (expensive: the most expensive third), zaporna (negative price). poradi_dne = 1 is the cheapest hour of the day.
  • p_zaporna — probability of a negative price in tenths. For published hours 0 or 1. A value of 0.1 means “at most 10 %”, 0.9 “at least 90 %”.
  • pockat.levneji_pozdeji (cheaper later) — how likely it is that a window at least 0.30 CZK/kWh cheaper than the best known window appears in the coming days: nizka (low), stredni (medium), vysoka (high). In the beta in words only (beta: true); we will add a number once it has been validated over a longer period.
  • jistota (confidence) of a window — vysoka (all hours published), stredni (within 3 days), nizka (further ahead).
  • stav (status) — ok, or stara_data (stale data) when the data is older than 30 hours. stari_min = age in minutes.
ted.json (shortened)
{
  "verze": "1",
  "beta": true,
  "stav": "ok",
  "vydano": "2026-11-18T14:15:00+01:00",
  "vytvoreno": "2026-11-18T14:21:10+01:00",
  "dalsi_aktualizace": "2026-11-19T06:30:00+01:00",
  "stari_min": 42,
  "mena": "CZK",
  "jednotka": "Kc/kWh",
  "kurz_eur": 24.38,
  "uroven_klice": "beta",
  "strategie": "p50",
  "tarif": { "pouzit": true, "dph": true },
  "cena_ted": 4.012,
  "spot_ted": 2.31,
  "uroven_ted": "levna",
  "levno_ted": true,
  "zmena_urovne_v": "2026-11-18T16:00:00+01:00",
  "okno_3h": {
    "od": "2026-11-19T12:00:00+01:00", "do": "2026-11-19T15:00:00+01:00",
    "cena": 1.84, "cena_p10": 1.84, "cena_p90": 1.84,
    "jistota": "vysoka", "koncova": 3.41, "za_min": 1305
  },
  "p_zaporna_dnes": 0,
  "pockat": {
    "beta": true, "delka": 3, "rozdil": 0.3,
    "nejlepsi_znama": { "od": "2026-11-19T12:00:00+01:00", "do": "2026-11-19T15:00:00+01:00", "cena": 1.84 },
    "levneji_pozdeji": "stredni"
  },
  "poradi_ted": 3,
  "n": 4,
  "v_n_nejlevnejsich": true,
  "nejlevnejsi_hodina": {
    "dnes":  { "base": 13, "peak": 13, "offpeak": 3, "zdroj": "trh" },
    "zitra": { "base": 12, "peak": 12, "offpeak": 2, "zdroj": "trh" }
  }
}

Daily signals

For simple switching without your own logic, ted.json (and loxone.txt) carries signals computed within the day from your price (final price with a tariff, otherwise spot):

  • poradi_ted — rank of the current hour among the hours of the day, 1 = cheapest.
  • v_n_nejlevnejsich — is the current hour among the n cheapest hours of the day? Parameter n (1–24, default 4).
  • nejlevnejsi_hodina — local hour (0–23) with the lowest price for the whole day (base, 0–24 h), for peak (peak, 8–20 h) and off-peak (offpeak, 20–8 h), today and tomorrow. Tomorrow is filled in as soon as we know it from published prices or from the forecast (zdroj).

Battery plan (recommendation only)

baterie.json suggests for every hour whether to charge the battery from the grid, discharge it into the house or hold, and computes the expected state of charge and the savings compared with doing nothing. You provide capacity (kWh), power (kW), current state of charge (%), the limits soc_min/soc_max, efficiency, wear cost (CZK per kWh delivered from the battery) and the horizon (default 24 h, at most 48 h).

baterie.json (shortened)
curl "https://api.itexservices.cz/v1/k/its_…/baterie.json?kapacita=10&vykon=5&soc=50&opotrebeni=0.5"
response (shortened)
{
  "jen_doporuceni": true,
  "akce_ted": "drzet",
  "hodiny": [
    { "od": "2026-11-18T02:00:00+01:00", "cena": 1.2, "akce": "nabijet",
      "nabiti_kwh": 4.743, "vybiti_kwh": 0, "soc_konec": 100 },
    { "od": "2026-11-18T08:00:00+01:00", "cena": 5.4, "akce": "vybijet",
      "nabiti_kwh": 0, "vybiti_kwh": 4.981, "soc_konec": 47.5 }
  ],
  "ekonomika": { "uspora": 12.66, "naklad_nabijeni": 5.69, "hodnota_vybiti": 26.9,
                 "opotrebeni": 2.49, "srovnani": "nic_nedelat", "cil_splnen": true }
}

The model is deliberately simple: it does not know the house consumption, PV production, reserves or the grid state. A discharged kWh is worth the price of its hour (it covers consumption you would otherwise buy). At the end of the horizon the battery should hold at least soc_konec (default = current state).

This is a recommendation, not control. The response carries jen_doporuceni: true. Whether and how you use the plan is your decision and your responsibility — control the inverter and battery with the manufacturer’s safeguards.

Negative-price alerts

For a key (in the ITexLink app, My account) you can enable an e-mail when the feed-in or purchase price drops below a chosen threshold. We send it after tomorrow’s prices are published, at most once a day per key, and only based on published prices — the forecast does not go into e-mails. Every e-mail has a one-click unsubscribe link. The e-mails are in Czech.

Examples

curl
curl https://api.itexservices.cz/v1/k/its_…/ted.json

# cheapest 4-hour window until tomorrow morning
curl "https://api.itexservices.cz/v1/k/its_…/okna.json?delka=4&do=2026-11-20T06:00"

# text for Loxone
curl https://api.itexservices.cz/v1/k/its_…/loxone.txt

# alternative: key in the header (not cached)
curl -H "Authorization: Bearer its_…" https://api.itexservices.cz/v1/ted.json
Python
import requests

KEY = "its_…"
r = requests.get(f"https://api.itexservices.cz/v1/k/{KEY}/ted.json", timeout=10)
r.raise_for_status()
d = r.json()
print(d["cena_ted"], d["uroven_ted"], d["okno_3h"]["od"])
JavaScript (Node.js 18+)
const KEY = "its_…";
const r = await fetch(`https://api.itexservices.cz/v1/k/${KEY}/schedule.json?hodin=3`);
if (!r.ok) throw new Error(`ITexSpot ${r.status}`);
const { aktivni_ted, unix } = await r.json();
// unix = [[start, end], …] in seconds — e.g. for a Shelly script

Schedule and grid export

schedule.json?hodin=4 picks the four cheapest hours of every day. For target charging enter kwh=10&kw=3.7&do=2026-11-20T06:00 (optionally ucinnost=0.9 for efficiency) — it picks as many of the cheapest hours before the deadline as the charge needs. pod=1.5 adds every hour priced below the threshold. The response carries aktivni_ted (active now), dalsi_od (next start), and intervals in ISO and as unix pairs for Shelly.

export.json?poplatek=0.5&prah=0 returns the hours when the feed-in price (spot − fee) drops below the threshold — exporting surplus to the grid does not pay off then. Otherwise the fee is taken from the key’s tariff.

Errors

CodestavWhen
401neplatny_klicThe key is missing, malformed or revoked.
422neplatny_parametrUnknown parameter or value out of range.
429limitLimit exceeded. The Retry-After header says after how many seconds to try again.
503nedostupneTemporary outage. Try again in a few minutes (Retry-After).

A JSON error looks like {"verze":"1","stav":"limit","chyba":"…"} (the message in chyba is in Czech). The Loxone text output carries the lines stav_kod=… and stav=… even on error, so the error does not hide behind a zero.

Limits and fair use

  • 60 requests per hour and 500 per day per key (Free tier 300 per day), at most 3 active keys per account.
  • On top of that, a limit of 30 requests per minute from one IP address applies, whatever key you send (also for stav.json). After 10 invalid key attempts within 10 minutes from one address we answer 429 until that period ends.
  • Recommended interval: Loxone 300 s, Home Assistant 20 min, evcc 1 h, Node-RED and Shelly 15–60 min. The data changes three times a day, polling faster does not help. All our guides fit within the Free tier limit.
  • Responses can be cached according to the Cache-Control header; a URL with the key in the path is cached on our side too. A response to a request with the Authorization header is never cached on our side.
  • A revoked key stops working within 15 minutes at the latest. Responses already in the cache (key in the path) live until they expire, at most 30 minutes.
  • Version 1 is stable: new fields may be added, but none will disappear or change meaning. A change would come as /v2 and /v1 would keep running for at least 12 months.

Safe behavior during an API outage

The API may stop responding for a while, return an error or return stale data. Your home automation has to expect this — build it so that an outage breaks nothing:

  • The relay stays in its last safe state. Without valid data, do not switch anything on because of a “cheap hour”. Return devices to the behavior the house would have without ITexSpot (boiler on a time schedule, inverter without export limiting, battery in normal mode).
  • Fallback window. For loads that must run (boiler, charging), keep a fixed window in usually cheap hours, for example 1–5 am. When the data is not valid, run by that window.
  • Detect invalid data. Always check the data status. In JSON it is stav (ok, stara_data = stale data, limit, neplatny_klic = invalid key, nedostupne = unavailable), in the Loxone text output stav_kod: 0 = OK, 1 = stale data, 401 key, 429 limit, 503 outage. Then stari_min (age in minutes): the data changes three times a day, so overnight it is routinely up to about 16 hours old. A value above 1,800 minutes (30 h) means no new data is being produced.
  • A lost connection may not show in the values. Loxone and other systems keep the last value they read when the server is unreachable. stari_min, however, grows with every successful request. When it stops changing, requests are not getting through.
  • On a 429 or 503 error, wait as long as the Retry-After header says and do not retry immediately.
Loxone — logic (in words, wire the blocks to suit your project)
valid   = (stav_kod = 0) AND (stari_min < 1800) AND (stari_min changed within 20 min)
boiler  = valid ? levno_ted : fallback_window   ← fallback window = time schedule 1–5 am
export  = valid ? limit by price : DO NOT LIMIT (inverter default behavior)
Home Assistant — data validity and fallback window
template:
  - binary_sensor:
      - name: "ITexSpot data valid"
        unique_id: itexspot_data_platna
        state: >-
          {{ has_value('sensor.itexspot_cena_ted')
             and state_attr('sensor.itexspot_cena_ted', 'stav') == 'ok'
             and (state_attr('sensor.itexspot_cena_ted', 'stari_min') | int(99999)) < 1800 }}

automation:
  - alias: "Boiler: cheap hours, fallback window 1–5 am when data is invalid"
    triggers:
      - trigger: time_pattern
        minutes: "/5"
    actions:
      - variables:
          turn_on: >-
            {% if is_state('binary_sensor.itexspot_data_platna', 'on') %}
              {{ is_state('binary_sensor.itexspot_levno_ted', 'on') }}
            {% else %}
              {{ 1 <= now().hour < 5 }}
            {% endif %}
      - action: "{{ 'switch.turn_on' if turn_on else 'switch.turn_off' }}"
        target:
          entity_id: switch.boiler
Shelly — script with schedule and fallback window
// Shelly Gen2+ (script): relay by the ITexSpot schedule, fallback window on outage
let URL = "https://api.itexservices.cz/v1/k/its_YOURKEY/schedule.json?hodin=4";
let intervals = [];   // [[start, end], …] in unix seconds
let validUntil = 0;   // until when we trust the schedule

function fallbackWindow(h) { return h >= 1 && h < 5; }

function decide() {
  let t = Date.now() / 1000;
  let on = false;
  if (t < validUntil) {
    for (let i = 0; i < intervals.length; i++) {
      if (t >= intervals[i][0] && t < intervals[i][1]) on = true;
    }
  } else {
    on = fallbackWindow(new Date().getHours());
  }
  Shelly.call("Switch.Set", { id: 0, on: on });
}

function load() {
  Shelly.call("HTTP.GET", { url: URL, timeout: 15 }, function (r, err) {
    if (err !== 0 || !r || r.code !== 200) return;   // keeps the last schedule
    let d = JSON.parse(r.body);
    if (d.stav !== "ok") return;
    intervals = d.unix;
    validUntil = Date.now() / 1000 + 24 * 3600;
  });
}

load();
decide();
Timer.set(60 * 60 * 1000, true, load);   // schedule every 1 h = 24 requests a day
Timer.set(60 * 1000, true, decide);      // decided locally, no network needed
The forecast is indicative information, not a guarantee. Your home automation must cope with the API not responding for a while — set a sensible default and watch the age of the data. Details are in the API terms.