Your systems authenticate with an API key, then read devices, series, telemetry and alarms over HTTPS. Your side opens every connection, so there is no inbound firewall rule and nothing to install. Select an endpoint to see its parameters, an example call and every response it can return.
BASE="https://api-cortex.aid-iot.com"
# 1. Authenticate. The token, not the key, goes on every later call.
TOKEN=$(curl -s -X POST "$BASE/v1/auth/token" \
-H "Content-Type: application/json" \
-d '{"apiKey":"'"$AID_API_KEY"'"}' | jq -r .token)
# 2. Confirm which organisation it resolved to.
curl -s "$BASE/v1/summary" -H "Authorization: Bearer $TOKEN"
# 3. Discover what actually holds data.
curl -s "$BASE/v1/telemetry/series" -H "Authorization: Bearer $TOKEN"
# 4. Read seven days of one series at ~600 points.
curl -s -G "$BASE/v1/telemetry" -H "Authorization: Bearer $TOKEN" \
--data-urlencode "deviceId=clean-b-temp-04" \
--data-urlencode "metric=temperature" \
--data-urlencode "from=2026-09-01T00:00:00Z" \
--data-urlencode "to=2026-09-08T00:00:00Z" \
--data-urlencode "agg=avg" --data-urlencode "width=600"One call, one bearer token. Every other request carries it.
What your organisation has: the estate, and the series that actually hold data.
The principal endpoint: one series, one range, at the resolution you ask for.
Read what needs attention, and acknowledge it from your own console.
Ask for a newly installed device to be registered.
How errors behave, what the budgets are, and how to keep a mirror in step.
This is the whole contract: every endpoint above, and every rule that spans them. Anything you cannot find here, write to [email protected] and we will answer it — and then add it to this page.