Company Name to Domain API
Find the website behind every company name from your AI assistant, no-code workflow or own code.
- From $0.001 per Domain
- Domain and Full URL
- 10,000 Domains per Task
| Company name |
|---|
| Brightwave Analytics |
| Northpeak Logistics |
| Juniper & Vale Studio |
Trusted by 38,000+ users at startups and Fortune 500 teams
Works with any tool that can send HTTP requests
Claude
Cursor
Codex
Make
n8n
Zapier
- Your own code
Pick Your Way In
Let an AI assistant or your automation tool do the setup, or call the REST API from your own code.
Paste the setup prompt
Copy the prompt for Claude Code, Codex or Cursor, or for Make, n8n or Zapier, and paste it in. The AI creates a Datablist folder on your computer and sets everything up.
Paste your API key
When the AI asks, copy your API key from the Datablist app and paste it into the .env file it opened. Never paste it into the chat.
Get your results
Send your list of names and get one row back per name: domain, website and a confidence level, ready for your sheet or CRM.
See a sample resultUsing Make, n8n or Zapier? Here is every field for the HTTP request
Use the HTTP request module or node your tool offers. You need three steps: send the list, wait, then read the results.
1. Send your list (HTTP request)
- Method
POST- URL
https://api.datablist.com/v1/enrichments/tasks- Headers
X-API-Key= your API keyContent-Type=application/json- Body (JSON)
- json{"enrichmentId": "company-name-to-domain","uniqueId": "company-name-to-domain-import-1","settings": {"workflow": "dataset_google","searchCountryCode": "US"},"inputs": [{"inputId": "row-1", "data": {"companyName": "Brightwave Analytics"}},{"inputId": "row-2", "data": {"companyName": "Northpeak Logistics"}},{"inputId": "row-3", "data": {"companyName": "Juniper & Vale Studio"}}]}
- Keep
- The
@idfrom the response. That is your task ID.
2. Wait until it is done
Add a short wait or delay, then a GET request to https://api.datablist.com/v1/enrichments/tasks/TASK_ID with the same X-API-Key header. Repeat until status is completed.
3. Read the results
GET https://api.datablist.com/v1/enrichments/tasks/TASK_ID/results?limit=50. Map outputs to your columns. If nextCursor is not empty, call again with &cursor= plus that value.
At a Glance
Return the domain and website matching the name. Filter on country to narrow results. Return the domain with the more traffic when several domains match. No Datablist workspace, collection or import needed.
What you give it
- Company names: One per row, straight from your list, sheet or CRM
- A country (optional): Narrows the search, for example US or France
- Where to search: Our company dataset, Google, or both
What you get back
- The domain: For example brightwaveanalytics.com
- The website: The full web address, ready to click
- A confidence level: High, Medium, Low or Very Low, so you know what to double-check
What it costs
- Found in our dataset: 1 credit, only when a domain is found
- Searched on Google: 2.5 credits per name searched
- 1,000 credits = $1: Shared with the Datablist app
What Teams Build With It
Put Company Name to Domain wherever your data already flows.
Complete accounts in your CRM
- New account in the CRM
- Domain saved on the record
Run the lookup whenever an account arrives without a website, so HubSpot, Salesforce or Pipedrive always has a domain to match on.
Feed your enrichment pipeline
- Company name
- Emails, firmographics, LinkedIn
The domain is the key most other enrichments need. Resolve it first, then pass it to company enrichment or an email finder.
Turn event lists into domains
- Trade show or partner list
- Deduplicated and routed
Turn the bare company names from trade show lists, partner exports or form fills into domains you can deduplicate and route.
What Will It Cost You?
Pay per lookup with credits. API access starts on the Growth plan.
How much will it cost you?
Tell us how many company names you need to resolve and we'll show you the cheapest way to get them.
= 1,450 credits: 700 database matches at 1 credit, 300 Google lookups at 2.5 credits
How credits work
1,000 credits = $1, so each credit costs a tenth of a cent. A database match costs 1 credit and is only charged when a domain comes back. A Google fallback lookup costs 2.5 credits and is charged either way, which is why the split between the two drives your bill. Google results are cached for 48 hours, so changing a setting and re-running inside that window costs 1 credit per row instead of 2.5. Plan credits renew monthly and reset if unused. Top-up credits never expire.
Build It Into Your Code
Everything you need to call the REST API directly: code, responses, endpoints, fields, authentication and limits.
datablist/company-name-to-domain-api
Official examples: cURL, Python with requests and HTTPX, and bulk CSV processing. Put your key in DATABLIST_API_KEY and run.
Copy, Paste, Run
A complete script that creates a task, waits for it and prints every result. Replace YOUR_PERSONAL_API_KEY with your key.
# 1. Create the task (returns 202 Accepted and the task "@id")
curl --request POST 'https://api.datablist.com/v1/enrichments/tasks' \
--header 'X-API-Key: YOUR_PERSONAL_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"enrichmentId": "company-name-to-domain",
"uniqueId": "company-name-to-domain-import-1",
"settings": {
"workflow": "dataset_google",
"searchCountryCode": "US"
},
"inputs": [
{"inputId": "row-1", "data": {"companyName": "Brightwave Analytics"}},
{"inputId": "row-2", "data": {"companyName": "Northpeak Logistics"}},
{"inputId": "row-3", "data": {"companyName": "Juniper & Vale Studio"}}
]
}'
# 2. Poll every few seconds until status is completed, failed or stopped
curl 'https://api.datablist.com/v1/enrichments/tasks/TASK_ID' \
--header 'X-API-Key: YOUR_PERSONAL_API_KEY'
# 3. Read the results, then follow nextCursor until it is null
curl 'https://api.datablist.com/v1/enrichments/tasks/TASK_ID/results?limit=50' \
--header 'X-API-Key: YOUR_PERSONAL_API_KEY'What the API Returns
One result per input, with your inputId, a status, the outputs and the credits used. Sample data.
{
"taskId": "00000000000040008000000000000001",
"results": [
{
"inputId": "row-1",
"status": "success",
"outputs": {
"companyDomain": "brightwaveanalytics.com",
"companyUrl": "https://www.brightwaveanalytics.com",
"domainConfidence": "High"
},
"creditsUsed": "1",
"error": null
}
],
"nextCursor": null
}Endpoints and Fields
All paths are relative to https://api.datablist.com. Field definitions come from GET /v1/enrichments/company-name-to-domain (schema version 2026-09-12).
View API schema (JSON) (opens in a new tab)
- /v1/enrichments/company-name-to-domain
- Read the schema, no key needed
- POST
- /v1/enrichments/tasks
- Create a task
- /v1/enrichments/tasks/{taskId}
- Poll status and progress
- /v1/enrichments/tasks/{taskId}/results
- Read results, 1 to 100 per page
- POST
- /v1/enrichments/tasks/{taskId}/stop
- Cancel a running task
- /v1/enrichments/tasks
- Task history, newest first
Schema Reference
Send settings once per task and one data object per input. Results can include extra fields as the enrichment evolves, so keep unknown keys when you parse outputs.
Show all settings, inputs and outputs
Settings
workflowWorkflow | Text | Datablist first uses a company dataset to match names with domains. Datablist might also perform a Google search on the remaining company names.Allowed values: |
|---|---|---|
searchCountryCodeTarget Country | Text | Narrow down the search to a specific country. This setting filters the company dataset and is a country setting for the Google Search fallback.Allowed values: |
countryOverwriteDefine target country per item. | Boolean | When enabled, a “Target Country” input will be added to configure the target country for each item. You can enter a country using its ISO 3166 code (Alpha-2 like “FR“, or Alpha-3 like “USA“) or its full English name (like “Portugal“). If the country is missing or invalid, Datablist will use the global “Target Country” setting as a fallback. |
acceptNonRootAccept non root websites | Boolean | By default, Datablist skips dataset and Google results that point to a page hosted below a domain the company does not own (eg: https://www.directory.com/mycompany). This is good to avoid company directories. But you can miss company websites that are hosted on platforms. For example: https://www.hostingplatform.com/mycompanypage. Use this setting to accept non-root websites while preserving and validating the full page URL. 👉 Datablist caches Google search results for 48 hours. If you change this setting after the first run, results come from the cache, costing only 1 credit. Enabled when: |
skipDomainsSkip following domains | Text list or Text | Additional domains to exclude when selecting company websites, as an array of domains. Enabled when: |
onlyProcessCachedResultsOnly Process Google Cached Results | Boolean | If enabled, Datablist will only use your saved Google search results from the cache. It won’t run new live searches. Use this to reduce costs and skip dataset results. Enabled when: |
Inputs (data)
companyNamerequiredCompany Name | Text | The name of the company to search for (ex: google). |
|---|---|---|
targetCountryTarget Country | Text | Narrow down the search to a specific country. This setting filters the company dataset and is a country setting for the Google Search fallback. If the country is missing or invalid, Datablist will use the global “Target Country” setting as a fallback. Enabled when: |
Outputs
companyDomainCompany Domain | Text | The company domain (ex: google.com), when found. |
|---|---|---|
companyUrlCompany Full Url | Text | The company full url (ex: https://www.google.com), when found.Format: |
domainConfidenceDomain Confidence | Text | Confidence level of the match: High, Medium, Low, or Very Low. |
One Header, Clear Limits
Create a Personal API Key in your Datablist account and send it on every authenticated request.
Authentication
Send your key in the X-API-Key header. Datablist exchanges and renews access tokens for you.
- Header:
X-API-Key: YOUR_PERSONAL_API_KEY - Optional: manage tokens yourself with
Authorization: BearerfromPOST /v1/account/token - One or the other: sending both headers returns
400 AmbiguousCredentials - Server side only: keep keys out of URLs, browser code and logs
Limits
- Inputs per task: 1 to 10,000
- Size: 16 KiB per input, 10 MiB per request
- Run time: up to 24 hours per task
- Task creation: 10 requests per 60 seconds per account
- Polling and results: 120 requests per 60 seconds per operation
- Active tasks: about 20 at once per account
- Retention: tasks and results are kept for 90 days
Frequently Asked Questions
Everything you or your AI coding agent need to integrate the Company Name to Domain API: auth, request, polling, results, limits and retries.


