Sticky.io Python API Docs | dltHub

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

Last updated:

Sticky.io is a commerce and subscription management platform offering a RESTful API for interacting with orders, products, customers, and subscriptions. The REST API base URL is https://developer-v2.sticky.io/ and All requests require HTTP Basic Authentication using an API username and password..

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


What data can I load from Sticky.io?

Here are some of the endpoints you can load from Sticky.io:

ResourceEndpointMethodData selectorDescription
orders/v2/ordersGETdataRetrieve a paginated list of orders.
products/v2/productsGETdataRetrieve a paginated list of products.
customers/v2/customersGETdataRetrieve a paginated list of customers.
subscriptions/v2/subscriptionsGETdataRetrieve a paginated list of subscriptions.
product_bundle_index/v2/product_bundle_indexPOSTdataRetrieve active product bundles (max 60 requests per minute).

How do I authenticate with the Sticky.io API?

Authentication uses HTTP Basic Auth; send an Authorization header with the value "Basic <base64(username:password)>".

1. Get your credentials

  1. Log in to your Sticky.io dashboard.
  2. Navigate to API Accounts (or API Users) in the administration menu.
  3. Click Create New API User.
  4. Provide a name and assign the required permissions.
  5. After creation, the dashboard will display the API Username and API Password. Copy these values; the password will not be shown again, so store it securely.
  6. Use the credentials in your API client as described in the auth_summary.

2. Add them to .dlt/secrets.toml

[sources.stickyio_source] api_username = "your_api_username" api_password = "your_api_password"

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 Sticky.io 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 stickyio_pipeline.py

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

Pipeline stickyio_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset stickyio_data The duckdb destination used duckdb:/stickyio.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline stickyio_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 orders and products from the Sticky.io 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 stickyio_source(api_username=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://developer-v2.sticky.io/", "auth": { "type": "http_basic", "password": api_username, }, }, "resources": [ {"name": "orders", "endpoint": {"path": "v2/orders", "data_selector": "data"}}, {"name": "products", "endpoint": {"path": "v2/products", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="stickyio_pipeline", destination="duckdb", dataset_name="stickyio_data", ) load_info = pipeline.run(stickyio_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("stickyio_pipeline").dataset() sessions_df = data.orders.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM stickyio_data.orders LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("stickyio_pipeline").dataset() data.orders.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 Sticky.io 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.


Troubleshooting

Authentication Errors

If you receive a 401 Unauthorized response, verify that the Authorization header contains a correctly base64‑encoded username:password. Incorrect credentials or missing header will trigger this error.

Rate Limiting

The product_bundle_index endpoint is limited to 60 requests per minute. Exceeding this limit returns a 429 Too Many Requests response. Implement back‑off or request throttling to stay within the limit.

Pagination Issues

List endpoints return pagination metadata (current_page, next_page_url, etc.). Ensure your client follows the next_page_url for subsequent pages; ignoring pagination will result in incomplete data retrieval.

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 Sticky.io?

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