For the complete documentation index, see llms.txt. This page is also available as Markdown.

100ms

100ms is a live video infrastructure platform that lets developers embed real-time audio, video, and live streaming directly into their apps. It powers experiences like virtual classrooms, telehealth consultations, video conferences, and live events across web and mobile platforms.

Why connect 100ms to Coupler.io?

Connecting 100ms to Coupler.io lets you pull session, room, recording, and analytics data into your reporting stack automatically — no manual exports, no API coding required.

  • Track engagement at scale — export session and analytics event data to monitor participant behavior, session lengths, and platform usage over time.

  • Audit rooms and recordings — query room configurations, templates, and stored recordings to support compliance and capacity planning.

  • Flexible destinations — export to AI tools, Google Sheets, BigQuery, Looker Studio, or other supported destinations.

  • Scheduled refreshes — keep your dashboards up to date with automatic data syncs on your chosen schedule.

Prerequisites

  • A Coupler.io account

  • A 100ms account with API access (Management Token)

100ms is currently available as an Early Access source. You may need the 100ms_airbyte_source_feature flag enabled on your Coupler.io account. Contact support if the source isn't visible in your workspace.

Quick start

How to connect

1

In Coupler.io, create a new data flow and search for 100ms in the source list.

2

Enter your 100ms Management Token. You can generate this from the 100ms dashboard under Settings → Developer.

3

Choose the data entity you want to export — for example, Sessions, Rooms, Recordings, or Analytics events. Each entity is exported in a separate data flow.

4

Set the Start date using the date picker to define the earliest date for your data export.

5

Choose your destination and run the import.

What data is available?

The 100ms source gives you access to your workspace's operational and usage data: rooms, the sessions that happened inside them, participants who joined, recordings that were stored, and the analytics events generated during those sessions. You can also pull the room template configurations that define how your video experiences are set up.

When to use it

Use the 100ms source when you need to analyze how your video platform is being used — session volume trends, participant counts, recording activity, or engagement events. It's also useful for auditing room configurations and template setups across your 100ms workspace.

Available entities

Sessions

Individual video call sessions. A session starts when the first peer joins a room and ends when the last peer leaves.

Field
Description

id

Unique session identifier

room_id

ID of the room where the session took place

created_at

Timestamp when the session was created

peers

List of participant objects in the session

duration

Total session duration

started_at

Timestamp when the first peer joined

stopped_at

Timestamp when the last peer left

Rooms

Virtual meeting rooms in your 100ms workspace. Each room can host multiple sessions over its lifetime.

Field
Description

id

Unique room identifier

name

Room name

description

Optional room description

customer_id

ID of the workspace/account

template_id

ID of the room template applied

enabled

Whether the room is currently active

created_at

Room creation timestamp

updated_at

Last modification timestamp

Active room peers

Participants currently connected to rooms in real time. Useful for monitoring live usage.

Field
Description

id

Peer identifier

room_id

Room the peer is connected to

session_id

Current session identifier

name

Peer display name

role

Peer's role in the room

joined_at

Timestamp when the peer joined

user_id

Your application's user identifier for this peer

Templates

Room configuration templates that define the settings and layout applied when creating rooms.

Field
Description

id

Template identifier

name

Template name

customer_id

Workspace/account ID

created_at

Template creation timestamp

updated_at

Last modification timestamp

Template settings

The specific configuration parameters stored inside each room template, such as role definitions and permissions.

Field
Description

template_id

Parent template ID

roles

Role definitions and permission sets

settings

Room-level settings (recording, screenshare, etc.)

Templates destinations

Recording and streaming destination settings attached to a template — for example, where recordings are stored or where live streams are sent.

Field
Description

template_id

Parent template ID

destination_type

Type of destination (recording, live stream, etc.)

config

Destination-specific configuration

Analytics events

User interaction and engagement events captured during video sessions — joins, leaves, media toggles, and other in-session actions.

Field
Description

id

Event identifier

session_id

Session the event belongs to

peer_id

Peer who triggered the event

room_id

Room where the event occurred

type

Event type (e.g., peer.join, peer.leave)

created_at

Event timestamp

data

Additional event-specific payload

Recordings

Stored video recordings of completed 100ms sessions.

Field
Description

id

Recording identifier

room_id

Room where the recording was made

session_id

Session that was recorded

status

Recording status (e.g., completed, processing)

created_at

Recording creation timestamp

duration

Recording length

size

File size

url

URL to access the recording

Common use cases by role

Engineering / DevOps

Use Sessions and Analytics events to monitor platform health, detect abnormal drop-off rates, and correlate session failures with infrastructure events. Use Active room peers to track concurrency in real time.

Product managers

Use Sessions and Recordings to measure feature adoption — how often video sessions occur, how long they last, and which rooms are most active. Use Templates to understand how different room configurations are being deployed.

Customer success / Support

Use Sessions and Rooms to investigate specific customer issues — look up a session by ID, check when it started and stopped, and review which peers participated. Use Recordings to verify whether a session was successfully recorded.

Business analytics

Use Analytics events over time to build engagement funnels. Combine with Sessions data to understand drop-off, peak usage hours, and geographic patterns.

Platform-specific notes

  • Early Access: 100ms is an Early Access source in Coupler.io. Availability depends on a feature flag (100ms_airbyte_source_feature) on your account.

  • Start date required: All entities require a start date. Data before the start date will not be returned.

  • One entity per flow: Each data flow exports a single entity. Create separate flows for Sessions, Recordings, and Analytics events if you need all three.

  • Active room peers: This entity reflects current live state and is not historical. Running the flow at different times will return different results.

  • Session vs. room: A room persists across many sessions. Filter by room_id in sessions to analyze a specific room's usage history.

100ms common issues

Connection

I can't find 100ms in the Coupler.io source list

100ms is an Early Access source and requires a feature flag to be enabled on your account. If you don't see it in the source list, contact Coupler.io support and ask them to enable the 100ms_airbyte_source_feature flag for your workspace.

Authentication fails when I enter my Management Token

Make sure you're using a Management Token from the 100ms dashboard, not an app token or a peer token. Go to your 100ms dashboard → Settings → Developer and generate or copy your Management Token. Tokens are workspace-scoped, so confirm you're using the token for the correct 100ms workspace.

Missing data

My export returns no rows even though sessions exist

Check the Start date in your data flow settings. If the start date is set too recently (or in the future), no sessions will fall within the range. Adjust the date picker to a date before your earliest session.

Also note that the 100ms source is date-filtered — only records created on or after your start date are returned.

Active room peers shows no data

The Active room peers entity returns participants currently connected to rooms in real time. If no rooms have active participants at the moment the flow runs, the export will be empty. This entity reflects live state only — it does not return historical peer data.

To analyze historical participant data, use the Sessions entity instead, which includes the peers field with participant details from past sessions.

Recordings are missing for sessions I know were recorded

Recordings may take several minutes to hours to appear after a session ends, depending on the recording duration and processing queue. If a recording was recently completed, wait and re-run the flow. Recordings still in processing status may not appear as fully resolved rows until processing is complete.

Permissions

I'm getting a 401 Unauthorized or permission error

If your 100ms account is on a restricted plan, some entities (e.g., analytics data) may not be available. Check your 100ms plan to confirm API access to those endpoints.

Data discrepancies

Session counts in my export don't match the 100ms dashboard

The 100ms dashboard and the API may differ in how they aggregate sessions. The Coupler.io export uses the start date you specify — if your dashboard shows an all-time view but your export has a start date set to last month, the numbers will differ. Align the date range in both places before comparing.

Analytics event counts seem lower than expected

Analytics events are filtered by your start date just like other entities. Events that occurred before the start date are not included. If you changed the start date in your flow, the export only reflects the new range from that point forward.

Rate limits

My flow is running slowly or timing out

100ms API rate limits apply during data export. For large workspaces with many sessions or analytics events, exports may take longer than expected. Consider narrowing your start date window to reduce the volume of data fetched per run. If timeouts persist, contact Coupler.io support.

100ms FAQ

What is 100ms and what data can I export from it?

100ms is a live video infrastructure platform for building audio and video experiences in web and mobile apps. Via Coupler.io, you can export eight entity types: Sessions, Rooms, Active room peers, Templates, Template settings, Templates destinations, Analytics events, and Recordings. See data-overview.md for the full field list per entity.

Is 100ms available on all Coupler.io plans?

100ms is currently an Early Access source. Access requires the 100ms_airbyte_source_feature flag to be enabled on your Coupler.io account. If you don't see 100ms in your source list, reach out to Coupler.io support to request access.

What type of credentials do I need to connect?

You need a Management Token from your 100ms workspace. This is a server-side token with read access to your workspace data. You can find or generate it in the 100ms dashboard under Settings → Developer. Do not use app tokens or peer tokens — they don't have the necessary permissions.

Can I export data for all rooms at once, or do I need separate flows per room?

You can export all rooms (or all sessions) in a single flow — the 100ms source returns all records across your entire workspace, filtered only by start date. You don't need separate flows per room. If you want to analyze a specific room, filter by room_id in your destination spreadsheet or BI tool after export.

How far back can I fetch data?

You can set any start date using the date picker in the flow settings. The 100ms API doesn't enforce a maximum lookback period, but very large date ranges may result in slower exports. For the best performance, set your start date to the beginning of the reporting period you care about.

Why does Active room peers return no data?

Active room peers shows participants currently connected to rooms at the time the flow runs. If no rooms have active participants when your flow executes, the export will be empty. This entity does not store historical data.

For historical participant data, use the Sessions entity — it includes a peers field with information about all participants from past sessions.

Can I export recordings and get a download URL?

Yes — the Recordings entity includes a url field pointing to the stored recording file. Note that URLs may be time-limited or require 100ms authentication depending on your storage configuration. Check your 100ms dashboard for access control settings on recording storage.

How often should I refresh my 100ms data flows?

It depends on your use case. For operational dashboards tracking active sessions, refresh every few hours. For daily usage reports, once a day is sufficient. Avoid over-refreshing the Active room peers entity — it only reflects current state and frequent polling adds API load without historical benefit.

For scheduling recommendations, see best-practices.md.

Do Analytics events and Sessions share the same start date filter?

Yes — the start date you set in the flow applies to all entities and filters by the record's created_at timestamp. Both Sessions and Analytics events are filtered by this date. Make sure the start date is set to before your earliest session or event if you want complete data.

Can I combine 100ms data with other sources in Coupler.io?

Yes. You can use Coupler.io's Combining Data feature to merge 100ms exports with data from other sources. For example, you could join 100ms session data with CRM data to analyze video engagement by customer account.

Learn more in the Combining Data section of the Coupler.io documentation.

Last updated

Was this helpful?