Pagos Python API Docs | dltHub
Build a Pagos-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pagos BIN Data API is a service that returns detailed information for a given bank identification number (BIN). The REST API base URL is https://parrot.prod.pagosapi.com and All requests require an API key passed in the x‑api‑key 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 Pagos data in under 10 minutes.
What data can I load from Pagos?
Here are some of the endpoints you can load from Pagos:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
bins | /bins | GET | Retrieve details for a single BIN (6‑10 digits). | |
bins_multiple | /bins/multiple | GET | Retrieve details for multiple BINs in a single request. | |
bins_enhanced | /bins | GET | Same as bins but with enhanced=true query param for additional data. | |
status | /status | GET | Health‑check endpoint returning service status. | |
limits | /limits | GET | Returns current rate‑limit usage and quotas. |
How do I authenticate with the Pagos API?
Provide your API key in the x‑api‑key header for every request.
1. Get your credentials
- Log in to the Pagos developer portal.
- Go to the "API Keys" or "Credentials" section.
- Click "Create New API Key".
- Copy the generated key and store it securely.
- Use this key in the x‑api‑key header when calling the API.
2. Add them to .dlt/secrets.toml
[sources.pagos_bin_data_source] api_key = "your_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 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 Pagos 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 pagos_bin_data_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pagos_bin_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pagos_bin_data_data The duckdb destination used duckdb:/pagos_bin_data.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pagos_bin_data_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 bins and bins_multiple from the Pagos 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 pagos_bin_data_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://parrot.prod.pagosapi.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "bins", "endpoint": {"path": "bins"}}, {"name": "bins_multiple", "endpoint": {"path": "bins/multiple"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pagos_bin_data_pipeline", destination="duckdb", dataset_name="pagos_bin_data_data", ) load_info = pipeline.run(pagos_bin_data_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("pagos_bin_data_pipeline").dataset() sessions_df = data.bins.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pagos_bin_data_data.bins LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pagos_bin_data_pipeline").dataset() data.bins.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 Pagos 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 Errors
- Missing or invalid API key – The API returns a 401 Unauthorized response when the
x-api-keyheader is absent or contains an invalid key.
Rate Limiting
- Rate limit exceeded – Single BIN lookup (
/bins) is limited to 100 calls every 10 seconds; batch lookup (/bins/multiple) is limited to 6 calls every 10 seconds. Exceeding these limits returns a 429 Too Many Requests response.
Testing / Quota Bypass
- Requests using the BIN value
999999are treated as test calls and do not count toward your quota.
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 Pagos?
Request dlt skills, commands, AGENT.md files, and AI-native context.