Pipeliner Sales Python API Docs | dltHub
Build a Pipeliner Sales-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pipeliner Sales API documentation for creating products and product line items is available at https://developers.pipelinersales.com/api-docs/tutorials-and-articles/create-product-product-line-item. Authentication and API overview details are also provided on the site. The REST API base URL is https://<SERVICE_URL>/api/v100/rest/spaces/<SPACE_ID> and all requests use HTTP Basic authentication with an API application username and password (per-space API keys).
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 Pipeliner Sales data in under 10 minutes.
What data can I load from Pipeliner Sales?
Here are some of the endpoints you can load from Pipeliner Sales:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | entities/Accounts | GET | data | List Accounts (company records) |
| clients | entities/Clients | GET | data | Legacy/clients endpoint (example GET shown) |
| contacts | entities/Contacts | GET | data | List Contacts (people) |
| opportunities | entities/Opportunities | GET | data | List Opportunities (deals) |
| leads | entities/Leads | GET | data | List Leads |
| products | entities/Products | GET | data | List Products |
| product_categories | entities/ProductCategories | GET | data | List Product categories |
| product_price_lists | entities/ProductPriceLists | GET | data | List Product price lists |
| fields | entities/Fields | GET | data | List entity fields / metadata |
| sales_units | entities/SalesUnits | GET | data | List Sales units (organizational units) |
| master_rights | entities/MasterRights | GET | data | List Master rights / permissions |
How do I authenticate with the Pipeliner Sales API?
Create an API Application in your Pipeliner space to obtain a UserName and Password. Include them using HTTP Basic Auth (Authorization: Basic base64(username:password)). Space ID and Service URL (region host) are required in the request URL.
1. Get your credentials
- Sign in to your Pipeliner CRM space (https://crm.pipelinersales.com). 2) Open Administration → Unit, Users & Roles → Applications. 3) Create a new Application and click Show API Access. 4) Copy the generated User Name and Password (store securely). 5) Note the Space ID and Service URL shown for use in the base URL.
2. Add them to .dlt/secrets.toml
[sources.pipeliner_sales_source] username = "your_api_app_username_here" password = "your_api_app_password_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 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 Pipeliner Sales 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 pipeliner_sales_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pipeliner_sales_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pipeliner_sales_data The duckdb destination used duckdb:/pipeliner_sales.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pipeliner_sales_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 accounts and contacts from the Pipeliner Sales 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 pipeliner_sales_source(password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<SERVICE_URL>/api/v100/rest/spaces/<SPACE_ID>", "auth": { "type": "http_basic", "password": password, }, }, "resources": [ {"name": "accounts", "endpoint": {"path": "entities/Accounts", "data_selector": "data"}}, {"name": "contacts", "endpoint": {"path": "entities/Contacts", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pipeliner_sales_pipeline", destination="duckdb", dataset_name="pipeliner_sales_data", ) load_info = pipeline.run(pipeliner_sales_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("pipeliner_sales_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pipeliner_sales_data.accounts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pipeliner_sales_pipeline").dataset() data.accounts.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 Pipeliner Sales 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.
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 Pipeliner Sales?
Request dlt skills, commands, AGENT.md files, and AI-native context.