Ebeco Open API

Ebeco provides Open APIs that enable integration of our products into external systems, smart home solutions, and property platforms. Which Open API is used depends on the product model and the chosen integration method – cloud‑based or local direct integration with the thermostat.

Getting started

Follow these steps to use our Open API:

1. Select the correct network and enter the network password on the device
2. Download Ebeco Connect from the App Store or Google Play
3. Create a user account by following the instructions in the app
4. Create your own service or application using the documentation below

Overview – which API applies to which product?

Ebeco’s Open APIs are adapted to each product platform and use case.

Cloud Open API

For Wallflex 500/600 and EB-Therm 500

The Cloud Open API is used to integrate Ebeco’s connected products via Ebeco Connect and Ebeco’s backend. The API is suitable for solutions where multiple devices are managed centrally and integration is performed over the internet.

Used when you want to:

• Integrate Wallflex 500/600 or EB‑Therm 500 into external systems
• Work with cloud‑based control and monitoring
• Manage multiple installations or locations centrally

Technical specifications:

• REST API that expects and returns JSON data
• Authentication via Ebeco Connect 
• Communication via Ebeco’s backend

A complete reference of all methods and parameters is available in our Swagger-documentation.

Limitations

To prevent misuse of the API, the number of requests is limited per IP address to a total of 10 requests within 10 seconds and a total of 30 requests within 60 seconds.

If the request limit is exceeded, the API returns "HTTP 429 – Too Many Requests" for the remainder of the current period. When the period ends, the API will respond again.

Local Open API (BLE)

For EB Therm 300

The Local Open API is a local open API for direct communication with the EB‑Therm 300 thermostat via Bluetooth Low Energy (BLE). No internet connection or cloud service is required.

The API is intended for gateway solutions, embedded systems, and local control systems that require direct access to the thermostat.

Used when you want to:

• Integrate EB‑Therm 300 locally
• Communicate directly with the thermostat
• Avoid dependency on cloud services or the internet

Technical overview:

• Bluetooth Low Energy (BLE)
• Encrypted communication (PSK + AES‑GCM)
• Binary protocol adapted for embedded systems

Documentation – Download technical specification (.md)

Terms of use

The material provided via Ebeco’s Open APIs may not be used for distributing malicious code or in ways that could harm the Ebeco brand. We also require that Ebeco is stated as the source.

Available features and commands may vary depending on product model and firmware version. Some functions are restricted to Ebeco’s own applications and backend.