Czech bidding zone (CZ) only — prices in CZK, Czech distribution tariffs.
This English translation is provided for information only. The binding version is the Czech original: Podmínky užívání ITexSpot API.
1. Who operates the API
The ITexSpot API is operated by ITex Services s.r.o. (“we”). Contact: info@itexservices.cz. Matters not covered here are governed by our terms and conditions (part A) and our privacy policy (both in Czech).
2. Free beta
- The API is in a trial (beta) phase and is free of charge. Nothing is paid and nothing renews automatically.
- There is no legal entitlement to the availability, scope or duration of the beta. We may change, restrict or discontinue the API; we will announce significant changes by e-mail or on the documentation page.
- Should the API ever become paid, we will announce it in advance and the paid part will be governed by our terms and conditions. Anyone who does not want to pay will not lose their key suddenly — the key will move to a free tier with a smaller scope.
3. Key
- The key is personal and only for your own installation (home, company, your own devices).
- Do not share, publish or resell the key, and do not redistribute data from the API as your own service. If you want to integrate it into a product for other people, contact us.
- At most 3 keys can be active per account or e-mail address. A key can be revoked and a new one issued at any time. A revoked key stops working within 15 minutes at the latest; responses already in the cache may live until the end of their validity (at most 30 minutes).
- We do not store the key in readable form (only its fingerprint) — so we cannot recover a lost key, we can only issue a new one.
4. Limits and abuse
- Each key is limited to 60 requests per hour and 500 requests per day; on the free tier, 300 requests per day. Exceeding the limit returns error 429.
- We accept at most 30 requests per minute from a single IP address regardless of the key, and after 10 invalid key attempts within 10 minutes we temporarily reject the address (error 429).
- The data changes several times a day — poll sensibly (Loxone every 300 s, Home Assistant every 20 min, evcc every 1 h).
- Flooding the API, circumventing limits or security, trying keys that do not belong to you, and sharing a key are grounds for immediately blocking the key, or all keys of the account. We may restrict traffic from an address even without a key.
- Automated downloading of our web pages (scraping) instead of using the API is not permitted.
5. Indicative information, not a guarantee
- The forecast is an estimate. The actual price may differ from it significantly, including from the uncertainty band the API provides. We take published prices from public sources and are not liable for errors in them.
- To the extent permitted by law, we are not liable for damage resulting from control based on API data (a higher electricity bill, lost earnings, damage to equipment or unsuitable operation). How you use the data is your decision.
- Your control system must survive an API outage. Expect that the API may not respond, may respond with an error or with stale data: set a default behavior, watch
stari_minandstav_kod, and do not let anything depend on the API that could endanger safety or property during an outage. - Our ITexLink devices do not control according to this forecast; they control according to the prices the exchange has published for the next day.
6. Data sources and licenses
- Published day-ahead market prices: ENTSO-E Transparency Platform.
- EUR/CZK exchange rate: Czech National Bank.
- Weather forecast as a model input: among others, Open-Meteo (data CC BY 4.0).
- The forecast itself is our work. If you show data from the API to other people (e.g. on your website), credit the source as “ITexSpot, itexservices.cz” along with the sources above.
7. Personal data
For each key we record the e-mail address or account it belongs to, when it was issued and last used, and how many requests arrived per day. This serves operation, limits and protection against abuse. The key is not stored in full in our logs. If you enable low-price notifications for a key, we also record the e-mail address we send them to and when we sent them; you can turn them off at the key or via the link in every e-mail.
8. Changes to these terms
We may change these terms; the version published on this page applies. By using the API after a change, you agree to the new version. Version of 17 November 2026 (limits tightened the same evening; e-mail notifications and the validity period of a revoked key added).