Abstract Python API Docs | dltHub

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

Last updated:

Abstract API is a provider of multiple small REST APIs (email validation, IP intelligence, timezones, screenshots, VAT validation, etc.) that return JSON or binary responses. The REST API base URL is https://screenshot.abstractapi.com/v1/ and All requests require an api_key query parameter for authentication..

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


What data can I load from Abstract?

Here are some of the endpoints you can load from Abstract:

ResourceEndpointMethodData selectorDescription
website_screenshothttps://screenshot.abstractapi.com/v1GET(binary image)Returns a screenshot image of the supplied URL.
timezonehttps://timezone.abstractapi.com/v1GETdata.timezoneRetrieves timezone information for a given location.
vat_validationhttps://vat.abstractapi.com/v1GETdata.validValidates a VAT number and returns compliance details.
ip_intelligencehttps://ip.abstractapi.com/v1GETdata.ipProvides IP address intelligence such as location and ISP.
email_validationhttps://emailvalidation.abstractapi.com/v1GETdata.is_valid_formatValidates an email address format and deliverability.

How do I authenticate with the Abstract API?

Authentication is performed by including the api_key query parameter in the request URL; no Authorization header is required.

1. Get your credentials

  1. Sign up for an account at https://www.abstractapi.com/.
  2. Log in and navigate to the dashboard.
  3. In the dashboard, select the desired API (e.g., Website Screenshot, IP Intelligence).
  4. Click "Create API Key" or view the existing key.
  5. Copy the displayed API key and store it securely for use as the api_key query parameter.

2. Add them to .dlt/secrets.toml

[sources.abstract_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 Abstract 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 abstract_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline abstract_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 website_screenshot and timezone from the Abstract 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 abstract_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://screenshot.abstractapi.com/v1/", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "website_screenshot", "endpoint": {"path": ""}}, {"name": "timezone", "endpoint": {"path": "", "data_selector": "data.timezone"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="abstract_pipeline", destination="duckdb", dataset_name="abstract_data", ) load_info = pipeline.run(abstract_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("abstract_pipeline").dataset() sessions_df = data.website_screenshot.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM abstract_data.website_screenshot LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("abstract_pipeline").dataset() data.website_screenshot.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 Abstract 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 the api_key query parameter is missing or invalid, the API returns a 401 Unauthorized response. Ensure the correct key is supplied as documented.

TLS / Protocol Errors

All requests must use TLS 1.2 or higher. Older TLS versions will result in a connection failure.

HTTP Status Codes

The API uses standard HTTP status codes to indicate success (200) or various error conditions (4xx for client errors, 5xx for server errors). Review the response body for additional error details.

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 Abstract?

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