Store Leads Python API Docs | dltHub

Store Leads is a data platform that indexes ecommerce stores, their installed apps, technologies, products and related metadata and exposes this data via a REST API. The REST API base URL is https://storeleads.app/json/api/v1/all and all requests require a Bearer API key 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 Store Leads data in under 10 minutes.

---

What data can I load from Store Leads?

Here are some of the endpoints you can load from Store Leads:

---

How do I authenticate with the Store Leads API?

Include header Authorization: Bearer <your.api.key> on all requests over HTTPS. API keys are created on the Account -> API tab.

1. Get your credentials

1. Log into your Store Leads account. 2) Open Account (or Account settings) page. 3) Open the API tab. 4) Generate/copy the API key. 5) Use it as a Bearer token in the Authorization header.

2. Add them to .dlt/secrets.toml

Copy
[sources.store_leads_source]
api_key = "your_storeleads_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Store Leads 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:

Copy
python store_leads_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline store_leads_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 domains and apps from the Store Leads API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def store_leads_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://storeleads.app/json/api/v1/all",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "domains", "endpoint": {"path": "domain", "data_selector": "domains"}},
            {"name": "apps", "endpoint": {"path": "app", "data_selector": "apps"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="store_leads_pipeline",
        destination="duckdb",
        dataset_name="store_leads_data",
    )
    load_info = pipeline.run(store_leads_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):

Copy
import dlt

data = dlt.pipeline("store_leads_pipeline").dataset()
sessions_df = data.domains.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM store_leads_data.domains LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("store_leads_pipeline").dataset()
data.domains.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 Store Leads data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If the Authorization header is missing or invalid the API returns 4xx (unauthorized) errors. Verify you are using HTTPS and the header "Authorization: Bearer <API_KEY>".

Rate limiting (HTTP 429)

Endpoints are rate limited per account/subscription. If you receive HTTP 429, inspect the Retry-After header and back off for the specified seconds.

Pagination and cursor semantics

List endpoints use page/page_size or cursor-based pagination. Some endpoints return next_cursor in responses; pass cursor=<next_cursor> to fetch next page. Using cursor=all will trigger asynchronous generation and return HTTP 202 initially — poll the same endpoint until HTTP 200 and results are present. When using cursor=all consider for=jsonl to receive JSONL lines to avoid memory issues.

Export/stream errors

The domain-export endpoint streams JSONL and may return an inline JSON error object mid-stream. Check the initial meta object (expected_chunks) and verify you received all chunks; handle "error" documents in the stream.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack