Docs / Data sources / Iru (formerly Kandji)

Iru (formerly Kandji)

Business software

Built when you ask for it

Sync Iru (formerly Kandji) device, blueprint, app, and alert data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Iru connector syncs your Apple device-management data into analytics-ready tables in your data warehouse. Pull devices, blueprints, apps, and alerts from the Kandji API, with Ingest handling auth, pagination, and retries so the tables stay current. Kandji rebranded to Iru in 2026; the API and its documentation still operate under the Kandji name.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Devices
  • Blueprints
  • Apps
  • Alerts

How it gets built

  1. Choose Iru (formerly Kandji) when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Iru (formerly Kandji)'s documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Iru (formerly Kandji) itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Bearer token (tenant-level API token). An admin generates the token in the web app under Settings > Access > Add API Token; it's shown once.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Iru (formerly Kandji) connector?
Not as a finished connector yet. Ingest builds it from Iru (formerly Kandji)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Iru (formerly Kandji) data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Iru (formerly Kandji) API documentation: https://support.kandji.io/kb/kandji-api

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Iru (formerly Kandji)