SalesLoft Python API Docs | dltHub
Build a SalesLoft-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
SalesLoft is a revenue engagement platform providing a REST API to programmatically access and manage people, companies, cadences, activities and related CRM/engagement data. The REST API base URL is https://api.salesloft.com and All requests require a Bearer access token (OAuth 2.0) provided 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 pip install "dlt[workspace]" and start loading SalesLoft data in under 10 minutes.
What data can I load from SalesLoft?
Here are some of the endpoints you can load from SalesLoft:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| people | people.json | GET | data | List People objects |
| accounts | accounts.json | GET | data | List Account/Company objects |
| cadences | cadences.json | GET | data | List Cadence definitions |
| person_cadence_memberships | person_cadence_memberships.json | GET | data | List memberships of people to cadences |
| calls | calls.json | GET | data | List Call activity records |
| emails | emails.json | GET | data | List Email activity records |
| activities | activities.json | GET | data | List generic Activity objects |
| teams | teams.json | GET | data | List Team objects |
| users | users.json | GET | data | List User objects |
| opportunities | opportunities.json | GET | data | List Opportunity records |
How do I authenticate with the SalesLoft API?
SalesLoft uses OAuth 2.0. Include the access token in the Authorization header as: Authorization: Bearer <access_token>.
1. Get your credentials
- Log in to https://accounts.salesloft.com with the account that will own the OAuth app.
- Navigate to the OAuth Applications page: https://accounts.salesloft.com/oauth/applications.
- Create a new OAuth App, providing a name, redirect URI(s) and the required scopes.
- Record the client_id and client_secret shown after creation.
- Implement the OAuth 2.0 authorization code flow to exchange an authorization code for an access token (and refresh token) for the target account.
- (Legacy) If an API token is needed, contact SalesLoft support (support@salesloft.com) to request one.
2. Add them to .dlt/secrets.toml
[sources.salesloft_source] client_id = "your_client_id" client_secret = "your_client_secret" access_token = "your_access_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 SalesLoft 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 salesloft_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline salesloft_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset salesloft_data The duckdb destination used duckdb:/salesloft.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline salesloft_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 people and accounts from the SalesLoft 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 salesloft_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.salesloft.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "people", "endpoint": {"path": "people.json", "data_selector": "data"}}, {"name": "accounts", "endpoint": {"path": "accounts.json", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="salesloft_pipeline", destination="duckdb", dataset_name="salesloft_data", ) load_info = pipeline.run(salesloft_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("salesloft_pipeline").dataset() sessions_df = data.people.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM salesloft_data.people LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("salesloft_pipeline").dataset() data.people.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 SalesLoft data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication failures
If you receive 401 Unauthorized, verify your Authorization header: Authorization: Bearer <access_token>. Ensure the token is not expired; refresh it if possible. Confirm the OAuth app has the required scopes and that the token was issued for the correct SalesLoft account.
Rate limits
SalesLoft enforces rate limits on API requests. If you receive 429 Too Many Requests, back off and retry after the time indicated in the Retry-After response header. Implement exponential backoff for subsequent retries.
Pagination
Most list endpoints are paginated and return results under the data key along with pagination metadata (e.g., metadata or links). Use the provided pagination parameters (page, per_page or cursor links) to iterate through pages until no further results are returned.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 SalesLoft?
Request dlt skills, commands, AGENT.md files, and AI-native context.