100ms

Business software

Built when you ask for it

Sync 100ms room, session, and recording 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 100ms connector syncs your real-time video/audio infrastructure data into analytics-ready tables in your data warehouse. Pull rooms, sessions, recordings, and peers from the 100ms API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

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

  • Rooms
  • Sessions
  • Recordings
  • Peers

How it gets built

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

What you will need

Management token (JWT). Generate a management token from the app_access_key and app_secret shown on the 100ms dashboard's Developer section.

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 100ms connector?
Not as a finished connector yet. Ingest builds it from 100ms's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can 100ms 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.

100ms API documentation: https://www.100ms.live/docs/get-started/v2/get-started/security-and-tokens

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 100ms