Split Python API Docs | dltHub

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

Last updated:

Split is a feature flagging and experimentation platform that provides REST APIs to manage feature flags, environments, segments, attributes, and related resources. The REST API base URL is https://api.split.io/internal/api/v2 and All requests require either a Bearer token in the Authorization header or an API key in the x-api-key header depending on account migration status..

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


What data can I load from Split?

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

ResourceEndpointMethodData selectorDescription
splitsapi/v2/splitsGETsplitsList all feature flags (splits) in a workspace.
environmentsapi/v2/environmentsGETenvironmentsList all environments in a workspace.
segmentsapi/v2/segments/ws/{workspace-id}/environments/{environment-id-or-name}GETList segments in an environment.
change_requestsapi/v2/changeRequests/ws/{workspaceId}GETList change requests in a workspace.
workspacesapi/v2/workspacesGETworkspacesList all workspaces available to the organization.

How do I authenticate with the Split API?

Requests require an Authorization header with a Bearer token for Split-managed accounts. For accounts migrated to Harness, an x-api-key header is used instead.

1. Get your credentials

To obtain credentials for the Split REST API: 1. Log in to your Split or Harness Feature Management console. 2. Navigate to Admin Settings (or Account Settings). 3. Locate the API Keys section. 4. Click to create a new API key. 5. Select 'Admin' as the key type (this is required for management endpoints). 6. Provide a name, save the generated key securely, and copy it immediately as it will not be displayed again.

2. Add them to .dlt/secrets.toml

[sources.split_source] api_key = "your_admin_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 Split 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 split_pipeline.py

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

Pipeline split_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset split_data The duckdb destination used duckdb:/split.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 /workspaces and /environments/ws/{workspaceId} from the Split 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 split_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.split.io/internal/api/v2", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "splits", "endpoint": {"path": "api/v2/splits", "data_selector": "splits"}}, {"name": "environments", "endpoint": {"path": "api/v2/environments", "data_selector": "environments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="split_pipeline", destination="duckdb", dataset_name="split_data", ) load_info = pipeline.run(split_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("split_pipeline").dataset() sessions_df = data.splits.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM split_data.splits LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("split_pipeline").dataset() data.splits.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 Split 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 Split?

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