Reference · built on requestConnectorSensors, meters & gateways

Kaiterra

PM2.5, PM10, TVOC, CO2, temperature, and humidity from Kaiterra Sensedge and Sensedge Mini monitors, latest and historical.

Request accessPricing ↗

About

Kaiterra makes the Sensedge and Sensedge Mini, indoor air quality monitors with swappable sensor modules. They report PM2.5, PM10, TVOC, CO2, temperature, and relative humidity to the Kaiterra cloud over Wi-Fi or Ethernet. The API at api.kaiterra.com/v1 returns the latest reading, a history at intervals from one minute to one day, and device metadata including module lifetime.

Through Fibric, an operator reads each monitor on a schedule, compares the values with your limits, and proposes a ventilation change, a complaint reply, or a module replacement. The API has no write side, so every proposal is carried out in another system you approve.

This is a reference listing. It documents what Fibric would read from Kaiterra and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • The latest reading per device through GET /devices/{id}/top
  • History through GET /devices/{id}/history with begin, end, and group_by of 1m, 5m, 15m, 1h, 2h, or 1d, paged with _links.next
  • Parameters rpm25c, rpm10c, rpm1c, tvoc, rco2, rtemp, rhumid, plus ro3, co, no2, pir, atmospheric_pressure, and light on devices that carry them
  • Device metadata through GET /devices/{id}: model, firmware_version, home_region, and the hourly handshake with MAC addresses and serial number
  • Installed sensor modules and the fraction of useful lifetime each has left
  • Up to 100 reads in one call through POST /batch

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Know which rooms need more air

    rco2 history at 15m intervals shows the rooms that climb through the day. The operator proposes a ventilation change and reports the reading after it.

    With CO2 Ventilation

  • Answer an air quality complaint with the numbers

    When a complaint names a room, the operator pulls that device's top reading and the last day of history, then proposes a reply and a work order if a value is over your limit.

    With Comfort Complaint

  • Replace sensor modules before they drift

    GET /devices/{id} lists each installed module and its remaining lifetime. The operator proposes a module swap for any device below the fraction you set.

    With Calibration Due

  • Keep a daily air record per building

    Daily 1h averages for rpm25c, tvoc, and rco2 feed a per-building record. The operator proposes a notice when a site exceeds its target for consecutive days.

    With Indoor Air

Requirements

  • A Kaiterra account with Sensedge or Sensedge Mini devices and their UUIDs from the device settings or the Kaiterra app
  • For devices managed under an organization, an API key created by a member of that organization
  • HTTPS for every request; a missing or bad key returns HTTP 401
Authentication
An API key generated at app.kaiterra.com under Account Settings > API Keys, sent as the key URL parameter over HTTPS; Kaiterra advises rotating it yearly.

Limits

  • Read-only: the API has no endpoints to change device settings, so acts are carried out elsewhere
  • History responses stop near 10,000 items and continue through _links.next; the default window is one week before end
  • Rate limits are not stated in the API documentation
  • The rtvoc parameter is deprecated in favour of tvoc, with removal scheduled for October 2027

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Kaiterra ↗

Questions and answers

Are history timestamps the start or the end of the interval?
The end. A one hour average from 1pm to 2pm carries a timestamp of 14:00. Each series also states its span in seconds, so 60 means a one minute sample and 3600 an hourly average. All times are RFC3339 in UTC unless you pass time_zone.
Can any API key read any device?
No. Devices managed under an organization are restricted to that organization's members and the API keys they create; another key gets HTTP 403. Devices not added to an organization can be read by any API key, so treat a UUID as sensitive.
Can I fetch several devices in one request?
Yes. POST /batch takes a JSON array of up to 100 sub-requests, each with a method and relative_url such as /devices/{id}/top or /devices/{id}/history. Auth comes from the outer request. The response is an array of code and body pairs.
Ask about Kaiterra

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Kaiterra through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy