Entri Python API Docs | dltHub

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

Last updated:

Entri's API documentation provides details on domain management, SSL certificates, and custom domain support. The API supports automatic setup and domain propagation status tracking. For more information, visit https://developers.entri.com/api-reference. The REST API base URL is https://api.goentri.com and All requests require a JWT Bearer token 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 Entri data in under 10 minutes.


What data can I load from Entri?

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

ResourceEndpointMethodData selectorDescription
checkdomainavailability/checkdomainavailabilityGETChecks if a domain is available.
power/powerGETRetrieves power eligibility and CNAME target information.
ssl/sslGETReturns SSL certificate status and pagination info.
monitor_domains/monitor/domainsGETdomainsLists monitored domains and their status.
monitor_domain_detail/monitor/domains/{domain_name}GETRetrieves details and DNS records for a specific domain.
webhook_last/connect/webhooks/last/:job_idGETGets the most recent webhook notification for a job ID.
webhook_sample/webhooksGETExample payload format for webhook notifications.

How do I authenticate with the Entri API?

Obtain a JWT token from the token endpoint and include it as Authorization: Bearer <token> on each request. Also send the applicationId header with your application ID.

1. Get your credentials

  1. Log in to the Entri developer dashboard.
  2. Create or locate an existing application to obtain its Application ID and Secret.
  3. Send a POST request to https://api.goentri.com/token with a JSON body containing applicationId and secret.
  4. The response returns a JWT token; copy this token for use in API calls.

2. Add them to .dlt/secrets.toml

[sources.entri_source] token = "your_jwt_token_here" applicationId = "your_application_id_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 Entri 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 entri_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline entri_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 checkdomainavailability and power from the Entri 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 entri_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.goentri.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "checkdomainavailability", "endpoint": {"path": "checkdomainavailability"}}, {"name": "power", "endpoint": {"path": "power"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="entri_pipeline", destination="duckdb", dataset_name="entri_data", ) load_info = pipeline.run(entri_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("entri_pipeline").dataset() sessions_df = data.checkdomainavailability.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM entri_data.checkdomainavailability LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("entri_pipeline").dataset() data.checkdomainavailability.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 Entri 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.


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

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