Full documentation is available in this repo's Wiki. This README is a summary.
tadoº (https://www.tado.com/) is a german based company which offers a smart thermostat solution to control heating and air-conditioning in your home. They sell hardware and subscription based add-on services. These can be controlled via a mobile app or a webapp on their website.
The apps use a tado API which is available at https://my.tado.com/api/v2. tadoº allows third-party developers to use this API for their own projects, (see here) but they do not provide any kind of support or publish documentation.
This repository contains a community managed API definition for the tado API v2 which is hosted on https://my.tado.com/api. It uses OpenAPI v3.0.0 as its specification language. The API definition is based on the experience of software developers who are experimenting with the API to create their own solutions.
This API definition is not maintained or officially published by the tadoº company. The contents of this API definition is a best-effort product. There are no guarantees that this API definition is a complete and correct representation of the actual API as exposed via https://my.tado.com/api/v2.
As the owner of the repo I do not have any ties to the tadoº company. I simply like to create a space where knowledge about the tado API can be centralized and shared in a standardized form, so it becomes easier for software developers interested in home automation to use the API.
Links to the API definition in various formats:
- file in this GitHub repo: tado-openapispec-v2.yaml
- raw content: https://raw.githubusercontent.com/kritsel/tado-openapispec-v2/latest/tado-openapispec-v2.yaml
- Swagger UI: https://kritsel.github.io/tado-openapispec-v2/swagger.html
The tado API hosted on https://my.tado.com/api has limited support for tadoº X devices. Tadoº hosts a separate API geared towards tadoº X.
More info is available at https://github.com/kritsel/tado-openapispec-v2/wiki/tado-X
Without the groundwork done by Stephen C. Phillips (https://blog.scphillips.com/posts/2017/01/the-tado-api-v2/) and Terence Eden (https://shkspr.mobi/blog/2019/02/tado-api-guide-updated-for-2019/) I would have never started experimenting with the tado API, and this API definition would have never seen the light of day.
Additionally, the following GitHub members and repositories have been a great help:
- mattdavis90 Matt Davis: https://github.com/mattdavis90/node-tado-client
- clambin Christophe Lambin
- wmalgadey Wolfgang Malgadey: sharing information about tadoº X support
Feel free to submit a PR or create an issue if you want to contribute to this API definition.
Special request for owners of the new tado X hardware: if you have knowledge about any https://my.tado.com/ endpoints described in this definition which do not work as described, please create an issue (or submit a PR) with documentation improvement suggestions.