Skip to main content
The Compatibilities area lets you build an Aidoo compatibility selector. Given an indoor unit manufacturer and one of its models, it returns the Aidoo controller that must be sold to the client to complete the installation.
Every model resolves to a single article reference — the SKU your client needs to order. That reference is what the final step of the flow returns.

​
Aidoo types

Aidoo comes in several variants. Each request targets a single Aidoo type via the {article_type} path segment:
Availability depends on the market. Which Aidoo types exist is not fixed — it varies by app-market. Do not hardcode this table. Call List Aidoo types for the target market to discover which Aidoo types are actually available there.

​
The selection flow

1

List the available Aidoo types

Discover which Aidoo types are available in the target market, and present them as the first selector.List Aidoo types →
2

List the brands

For the chosen Aidoo type, retrieve the manufacturers that have at least one compatible indoor unit.List brands →
3

List the brand's compatible models

For the chosen brand, retrieve its compatible indoor unit models, including each model’s technical specs (heating and cooling power, airflow, communication protocol).Get a brand with its models →
4

Get the model detail and article reference

For the chosen model, retrieve its full detail. The article_reference field holds the SKU of the Aidoo controller to sell.Get the model detail →

​
Endpoints at a glance

List Aidoo types

The Aidoo types available in a market.

List brands

Manufacturers compatible with an Aidoo type.

Get a brand

A brand and all its compatible models.

Get a model

Full model detail with the Aidoo SKU.
Authentication, markets and locales are shared across the whole API — see Markets & locales. The endpoint pages assume you are already sending the required headers.