Splink Python API Docs | dltHub

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

Last updated:

Splink is a probabilistic record linkage library that also offers a REST API service for interacting with system functionalities such as tokens, roles, and payment requests. The REST API base URL is https://api.splink.io/ and All requests require an API key passed as a token..

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 Splink data in under 10 minutes.


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

ResourceEndpointMethodData selectorDescription
tokens/tokensGETEndpoint to manage authentication tokens.
roles/rolesGETManage user roles within the system.
packages/packagesGETInteract with package-related functionalities.
payments/paymentsGETHandle payment transactions.
company_members/company_membersGETManage company member information.
payment_requests/payment-requestsGETCreate and manage payment requests.

The API uses an API key for authentication, which is provided in the configuration object via an access token.

1. Get your credentials

  1. Navigate to the Splink platform dashboard at https://api.splink.io/. 2. Sign in to your account. 3. Locate the API/Developer settings section in your user profile or settings dashboard. 4. Select the option to generate a new API token or secret key. 5. Copy the generated API key and store it securely, as it will be required to authenticate your dlt data pipeline.

2. Add them to .dlt/secrets.toml

[sources.splink_source] api_key = "your_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 Splink 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 splink_pipeline.py

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

Pipeline splink_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset splink_data The duckdb destination used duckdb:/splink.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 token and payment-requests from the Splink 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 splink_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.splink.io/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "tokens", "endpoint": {"path": "tokens"}}, {"name": "roles", "endpoint": {"path": "roles"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="splink_pipeline", destination="duckdb", dataset_name="splink_data", ) load_info = pipeline.run(splink_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("splink_pipeline").dataset() sessions_df = data.tokens.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM splink_data.tokens LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("splink_pipeline").dataset() data.tokens.df().head()

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


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 Splink?

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