ITex Services s.r.o.

[ ITexSpot API · changelog ]

API changelog

What was added in each version and what you can rely on when you build automation on the API.

Beta · free · read-only key

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

Versioning rules

  • Adding a field to a response or a new optional parameter is NOT a version change. Clients must ignore unknown fields.
  • Removing a field or changing its meaning, unit or type means a new major version at /v2.
  • After /v2 is released, /v1 keeps running for at least 12 months. We will announce the end in advance by e-mail and on this page.
  • The version number in the specification (info.version) grows with every entry of this changelog; responses carry only the major version ("verze": "1").

The current shape of all endpoints is described in the API reference and the openapi.json specification.

1.1.0-beta · 17 November 2026

Daily signals for Loxone, inputs for Spot Price Optimizer, a recommended battery plan and negative-price alerts. Everything is backward compatible.

Added

  • loxone.txt — lines r00…r23 for the Spot Price Optimizer block in relative mode (inputs +0…+23); the VI_ITexSpot.xml template has matching commands.
  • ted.json and loxone.txt — rank of the current hour within the day (poradi_ted), an “among the N cheapest” flag (v_n_nejlevnejsich, parameter n, default 4) and the cheapest hour of the day for base, peak and off-peak, today and tomorrow (nejlevnejsi_hodina, in text nejl_dnes_base …).
  • baterie.json — recommended hourly battery plan (charge / discharge / hold, expected state of charge, savings compared with “do nothing”) including a wear cost. A recommendation only, not control.
  • Preset supplier tariffs for a key — selecting one fills in the supplier margin and the feed-in fee.
  • E-mail alert for a low or negative price (enabled per key): based only on published prices for tomorrow, at most once a day, one-click unsubscribe.
  • New documentation section “Safe behavior during an API outage” with examples for Loxone, Home Assistant and Shelly.

Changed

  • The recommended way to pass the key is in the path (/k/<klic>/…) — the response goes through the cache. The Authorization header (Bearer and Basic Auth) still works, it is just never cached.
  • The Home Assistant, Node-RED and evcc guides use the key in the path; the Home Assistant package polls less often (ted.json every 20 min, outlook every 4 h) so that it fits the Free tier limit too.
  • The server remembers a verified key for 15 minutes (previously 4): a revoked key stops working within 15 minutes at the latest, responses already cached live until they expire.
  • The API has its own address https://api.itexservices.cz/v1. The old address https://www.itexservices.cz/api/spot/v1/… temporarily redirects (308) to the new one, keeping the path and query — but please update it in Loxone, Home Assistant and your scripts.
  • The Free tier allows 300 requests a day (previously 100), so that Loxone polling every 300 s works even without the cache. The hourly limit is unchanged.
  • The OpenAPI specification comes in two languages with identical structure: openapi.json with English descriptions (the standard for tools) and openapi.cs.json in Czech.

Under consideration

  • Webhook alerts (your own URL that the API calls). Not yet: calling arbitrary URLs from our server carries a security risk that we want to handle properly first.

1.0.0-beta · 17 November 2026

First public version of API v1, in a free beta.

Added

  • vyhled.json — 7-day outlook by hour (or by quarter-hour for published prices) with a p10–p90 band.
  • ted.json — price and level now, the cheapest and most expensive 3-hour window, negative-price risk and “wait” (in words).
  • okna.json — the cheapest and most expensive non-overlapping windows of 1–12 h.
  • loxone.txt — name=value lines for the Virtual HTTP Input and the VI_ITexSpot.xml template.
  • evcc.json — custom tariff for evcc.
  • schedule.json — consumption schedule: N cheapest hours a day or target charging.
  • export.json — when to limit grid export based on the feed-in price.
  • stav.json — data status without a key.
  • Key in the path, in the Authorization: Bearer header or via Basic Auth.
  • Final price based on the tariff stored with the key.
  • Per-key and per-IP limits, errors 401, 422, 429 and 503 with a Retry-After header.
  • OpenAPI 3.1 specification (openapi.json).