TokBox Python API Docs | dltHub

Build a TokBox-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The TokBox REST API documentation provides reference for integrating video services, including session management and broadcasting. Essential elements include API keys, JSON web tokens for authentication, and REST endpoints for session operations. For detailed usage, refer to the official TokBox REST API reference. The REST API base URL is https://api.opentok.com and All requests require a JSON Web Token (JWT) sent in the X-OPENTOK-AUTH header..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading TokBox data in under 10 minutes.


What data can I load from TokBox?

Here are some of the endpoints you can load from TokBox:

ResourceEndpointMethodData selectorDescription
project_details/v2/project/{api_key}GETGet project details (single project)
projects_list/v2/projectGETGet all projects for account
archives_list/v2/project/{api_key}/archiveGETList archives for a project
archive_get/v2/project/{api_key}/archive/{archive_id}GETGet metadata for a single archive
sessions_create/v2/project/{api_key}/session/createPOSTCreate a session (response is a top‑level array with session object)
session_connections/v2/project/{api_key}/session/{sessionId}/connectionGETList connections in a session
session_streams/v2/project/{api_key}/session/{sessionId}/streamGETGet stream information (single or list endpoint)
broadcast_get/v2/project/{api_key}/broadcast/{broadcastId}GETGet info about a live broadcast
broadcasts_list/v2/project/{api_key}/broadcastGETList live streaming broadcasts

How do I authenticate with the TokBox API?

Create a short-lived JWT signed with your OpenTok API secret (HMAC-SHA256). Include the JWT in the X-OPENTOK-AUTH HTTP header for API calls. Use project-level API key/secret for most calls; account-level credentials are required for account-administration endpoints.

1. Get your credentials

  1. Sign in to your Vonage/OpenTok account (https://tokbox.com/account/).
  2. Create or open a project to find its API key and API secret on the Project page.
  3. Use the project API secret to sign JWTs (HS256). For account-level admin calls request the account-level API key and secret (available to account admins).

2. Add them to .dlt/secrets.toml

[sources.tokbox_source] api_key = "YOUR_OPENTOK_API_KEY" token = "YOUR_JWT_TOKEN"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the TokBox API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python tokbox_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline tokbox_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset tokbox_data The duckdb destination used duckdb:/tokbox.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline tokbox_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads archives and sessions from the TokBox API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def tokbox_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.opentok.com", "auth": { "type": "http_basic_jwt", "token": api_key, }, }, "resources": [ {"name": "archives", "endpoint": {"path": "v2/project/{api_key}/archive"}}, {"name": "sessions", "endpoint": {"path": "v2/project/{api_key}/session"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="tokbox_pipeline", destination="duckdb", dataset_name="tokbox_data", ) load_info = pipeline.run(tokbox_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("tokbox_pipeline").dataset() sessions_df = data.archives.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM tokbox_data.archives LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("tokbox_pipeline").dataset() data.archives.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load TokBox data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for TokBox?

Request dlt skills, commands, AGENT.md files, and AI-native context.