Load Revvity Signals data in Python using dltHub

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

Last updated:

Revvity Signals REST API provides programmatic access to Signals Research Suite data, including experiments, entities, and workflow operations. The REST API base URL is https://<tenant>.signalsresearch.revvitycloud.com/api/rest/v1.0/ and all requests require authentication via API key or OAuth bearer token passed in the 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 add "dlt[hub]" and start loading Revvity Signals data in under 10 minutes.


What data can I load from Revvity Signals?

Here are some of the endpoints you can load from Revvity Signals:

ResourceEndpointMethodData selectorDescription
users/usersGETRetrieves a list of users
entities/entitiesGETRetrieves a list of entities
entities_search/entities/searchPOSTSearch for entities with filters
material_libraries/materials/librariesGETList material library EIDs
samples/samples/{sampleId}/propertiesGETGet properties for a specific sample

How do I authenticate with the Revvity Signals API?

Authentication is required via the Authorization header using the 'Bearer' scheme, followed by the API key (e.g., 'Authorization: Bearer <API_KEY>'). Alternatively, an 'x-api-key' header can be used with the API key as the value.

1. Get your credentials

To obtain an API key for the Revvity Signals REST API, log in to your Signals instance as an administrator. Navigate to the Configuration menu, select System Settings, and then click on the API Key section. From there, select Add New API Key (or provide your email address if prompted), choose the associated user, and click Generate API Key. Note that keys must be associated with an existing user account in the tenant.

2. Add them to .dlt/secrets.toml

[sources.revvity_signals_source] api_key = "your_generated_api_key_here" # Include the following in your request headers: # Authorization = "Bearer your_generated_api_key_here"

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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Revvity Signals 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:

uv run python revvity_signals_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 /users and /entities/search/terms from the Revvity Signals 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 revvity_signals_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<tenant>.signalsresearch.revvitycloud.com/api/rest/v1.0/", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "entities_search", "endpoint": {"path": "entities/search", "data_selector": "data"}}, {"name": "users", "endpoint": {"path": "users", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="revvity_signals_pipeline", destination="duckdb", dataset_name="revvity_signals_data", ) load_info = pipeline.run(revvity_signals_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("revvity_signals_pipeline").dataset() sessions_df = data.entities_search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM revvity_signals_data.entities_search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("revvity_signals_pipeline").dataset() data.entities_search.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 Revvity Signals 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 harness:

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

Was this page helpful?

Community Hub

Need more dlt context for Revvity Signals?

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

Available Pipelines