RD Station Python API Docs | dltHub

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

Last updated:

RD Station is a platform offering REST APIs for managing marketing and CRM operations including contacts and conversions. The REST API base URL is https://api.rd.services/ and all requests require a Bearer token in the Authorization 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 RD Station data in under 10 minutes.


What data can I load from RD Station?

Here are some of the endpoints you can load from RD Station:

ResourceEndpointMethodData selectorDescription
crm_contacts/crm/v2/contactsGETList contacts
crm_deals/crm/v2/dealsGETList deals
crm_campaigns/crm/v2/campaignsGETList campaigns
crm_tasks/crm/v2/tasksGETList tasks
crm_products/crm/v2/productsGETList products

How do I authenticate with the RD Station API?

RD Station APIs use OAuth2 authentication. Requests require an 'Authorization' header with the value 'Bearer {access_token}' and a 'Content-Type' header set to 'application/json'.

1. Get your credentials

To obtain API credentials for RD Station Marketing: 1. Log in to your RD Station Marketing account. 2. Navigate to the App Store section within the dashboard. 3. Access the 'API Keys' management screen (note: this requires Manager or Owner access). 4. Click 'Generate Key' and provide a descriptive name for the integration. 5. Enable the key status and copy the generated key code. Note that for broader API access (full REST API), OAuth2 is required, which involves registering an application in the RD Station App Publisher portal to obtain a client_id and client_secret.

2. Add them to .dlt/secrets.toml

[sources.rd_station_source] rd_station_api_key = "your_api_key_here" # If using OAuth2: rd_station_client_id = "your_client_id_here" rd_station_client_secret = "your_client_secret_here" rd_station_refresh_token = "your_refresh_token_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 RD Station 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 rd_station_pipeline.py

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

Pipeline rd_station_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset rd_station_data The duckdb destination used duckdb:/rd_station.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 contacts and campaigns (these are frequently used entities across the Marketing and CRM v2 APIs) from the RD Station 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 rd_station_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.rd.services/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "crm_contacts", "endpoint": {"path": "crm/v2/contacts"}}, {"name": "crm_deals", "endpoint": {"path": "crm/v2/deals"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="rd_station_pipeline", destination="duckdb", dataset_name="rd_station_data", ) load_info = pipeline.run(rd_station_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("rd_station_pipeline").dataset() sessions_df = data.crm_contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM rd_station_data.crm_contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("rd_station_pipeline").dataset() data.crm_contacts.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 RD Station 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 RD Station?

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