Whois JSON API Python API Docs | dltHub

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

Last updated:

Whois JSON API provides RESTful services for domain information in JSON format, requiring an API token for access. It supports server-to-server communication via HTTPS. The API includes endpoints for retrieving domain details and status. The REST API base URL is https://whoisjsonapi.com/v1 and All requests require a Bearer token (Authorization header) or an apiKey query parameter..

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 Whois JSON API data in under 10 minutes.


What data can I load from Whois JSON API?

Here are some of the endpoints you can load from Whois JSON API:

ResourceEndpointMethodData selectorDescription
single_domain/v1/{domain}GETWHOIS lookup for a single domain (returns parsed WHOIS JSON).
bulk_domains/v1/domains?d={d1,d2,...}GETdomainsBulk WHOIS for up to 20 domains (comma‑separated).
domain_status/v1/status/{domainName}GETDomain availability check; returns {"domain":...,"status":...}.
nslookup/api/v1/nslookupGETDNS records (A, AAAA, MX, TXT, CNAME, NS, SOA).
ssl_cert_check/api/v1/ssl-cert-check?domain=...GETSSL/TLS certificate details for the given domain.
subdomains/api/v1/subdomains?domain=...GETSubdomain discovery (returns a list of subdomains).
reverse_whois/api/v1/reverseWhois?ip=...GETReverse WHOIS / IP‑to‑domain listing.

How do I authenticate with the Whois JSON API API?

Send your API token in the Authorization header as Bearer YOUR_API_TOKEN. Alternatively you may provide the token as the apiKey query parameter when supported.

1. Get your credentials

  1. Create a free account on the provider dashboard (WhoisJSONAPI). 2) After signup the API token is generated instantly and is shown on the Dashboard / My Products page. 3) Copy the token and use it as Authorization: Bearer YOUR_API_TOKEN or as apiKey query parameter.

2. Add them to .dlt/secrets.toml

[sources.whois_json_api_source] api_token = "YOUR_API_TOKEN"

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 Whois JSON API 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 whois_json_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline whois_json_api_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 single_domain and bulk_domains from the Whois JSON API 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 whois_json_api_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://whoisjsonapi.com/v1", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "single_domain", "endpoint": {"path": "v1/{domain}"}}, {"name": "bulk_domains", "endpoint": {"path": "v1/domains?d={domain1,domain2,...}", "data_selector": "domains"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="whois_json_api_pipeline", destination="duckdb", dataset_name="whois_json_api_data", ) load_info = pipeline.run(whois_json_api_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("whois_json_api_pipeline").dataset() sessions_df = data.single_domain.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM whois_json_api_data.single_domain LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("whois_json_api_pipeline").dataset() data.single_domain.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 Whois JSON API 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 Whois JSON API?

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