Connecting to Iru

Connecting to Iru

Iru is read with a tenant subdomain and an API bearer token.

What you need

Field	Where it comes from
Subdomain	Your tenant, e.g. acme
API Token	Issued from the Iru admin console

Subdomain handling

You can paste the bare tenant name, the dashboard URL, or the full API host — the app works out the right API endpoint either way, including EU-region tenants:

You enter	Resolves to
acme	acme.api.kandji.io
acme.kandji.io	acme.api.kandji.io
https://acme.kandji.io/devices/	acme.api.kandji.io
acme.api.kandji.io	acme.api.kandji.io
acme.eu.kandji.io	acme.api.eu.kandji.io
acme.api.eu.kandji.io	acme.api.eu.kandji.io

A leading https:// or http://, and any path after the host, are stripped. Case doesn't matter, and spaces or line breaks pasted around the subdomain or token are trimmed.

Iru needs a licence once the free trial has ended. This is checked again when you continue, in case the trial ran out while the screen was open.

Saved servers

If you report on more than one tenant, save each as a server profile (display name and subdomain) and reconnect without retyping anything. Saved profiles appear as buttons under Saved Servers on the sign-in screen. Click one to fill in the form. The server button (Manage saved servers) opens the manager, where you can add, edit and delete profiles.

Profiles are saved in the app's preferences, and each API token is kept in the Keychain. Deleting a profile asks you to confirm. Clear Saved also asks, and names any automated reports that rely on the saved credentials. Leaving Save to Keychain unticked doesn't delete credentials you saved before.

Connection test

The tool verifies the token against a cheap authenticated endpoint before continuing. The error message tells you what to check:

Error	Meaning
HTTP 401	Iru rejected the API token. Check the token and the tenant subdomain
HTTP 403	The token isn't allowed to read this data. Check its permissions in Iru Settings → Access → API Token

All Iru endpoints used are read-only. Paginated responses are followed automatically, up to 100 pages, and only ever on your tenant's own API host, so the token is never sent anywhere else. Throttled requests (HTTP 429) and brief outages (503, 504) are retried up to three times.

Features your plan doesn't include

Some sections read Iru features that depend on your plan or add-ons, such as Threat Detections and Vulnerabilities. If the API says a feature isn't available for your tenant or token, the section shows a neutral note saying so, not an error, and not an all-clear. A genuine failure (a bad token, a server error or a network problem) is still shown as an error.

Next

• Report Sections — the 15 Iru sections