The company name to domain and logo API returns matching company names, domains, and logo URLs as JSON. Requests require an issued API key, and one name can produce several candidates. Use the interactive finder for manual checks; use the API when your server needs to process the same lookup in code.
Updated
Loading Company Name to Domain and Logo API
This may take a moment.
How does the company name to domain API work?
The API accepts an authenticated company-name query and returns likely company identities as JSON, including the matched name, domain, and logo URL fields available for each candidate.
- 01
Send a name from your server
URL-encode the query, attach the issued API key, and keep that credential outside browser JavaScript and public repositories.
- 02
Parse the candidate array
Treat the response as possible matches rather than assuming the first company is always the one you intended.
- 03
Validate before saving
Compare the name and domain with your source record, handle an empty response, and store the reviewed result with a date.
What does the company identity API provide?
The page documents the current authenticated lookup contract and pairs it with the manual bulk finder above for testing names before integration.
Company-name query
Use a human-readable company name as the lookup input.
JSON response
Receive machine-readable candidate objects for server-side processing.
Matched company name
Keep the normalized name returned with each candidate.
Official-domain candidate
Use the domain as the main identity field to validate before enrichment.
Logo URL
Receive the associated logo URL when the candidate includes one.
Authenticated access
Protect the issued API key and follow the current account quota and terms.
What is our expert’s verdict on the company API?
I use a company-name lookup to propose identities, then make the domain the field a person or a second rule must confirm. That keeps a fuzzy name from silently contaminating CRM or enrichment data. The limitation is inherent to the input: company names are not unique, some businesses share brands, and a logo URL can change after a rebrand.View Emre Elbeyoglu's profile
How does our expert integrate company identity data?
Emre Elbeyoglu's working notes
- 01
Keep the key on the server
Route requests through a backend or protected job so the credential is not exposed in browser source or logs.
- 02
Store the original query
Preserve what the user or source system supplied beside the matched company and domain.
- 03
Score ambiguous matches
Use country, email domain, website, or parent-company evidence when more than one candidate is plausible.
- 04
Handle empty arrays normally
A no-match result is a data outcome, not necessarily a system error; keep the record unresolved for review.
- 05
Cache reviewed identities
Avoid repeating the same request in one workflow, but attach a review date so stale domains and logos can be refreshed.
What problem does a name-to-domain API solve?
A company name is convenient for people but unreliable as a database key. Names can be shared, abbreviated, translated, or reused by subsidiaries. A likely official domain gives the record a stronger web identity and creates a base for later enrichment.
The API should still be treated as candidate generation. The caller owns the final match decision.
How should an authenticated request be made?
Send the query from server-side code, URL-encode the company name, and attach the API key issued for your account. A basic request follows this shape:
curl 'https://api.growthmarketing.ai/?query=example%20company' \
-H 'X-API-Key: YOUR_API_KEY'
A successful response is a JSON array of candidate objects:
[
{
"name": "Example Company",
"domain": "example.com",
"logo": "https://api.growthmarketing.ai/logo/example.com"
}
]
Do not put a real key in a public repository, browser bundle, shared screenshot, or analytics event.
How should multiple company matches be resolved?
Use evidence already present in the source record:
| Evidence | Match check |
|---|---|
| Work email | Does its domain match the candidate? |
| Country or city | Does the official site describe the same entity? |
| Product name | Does the candidate own or publish that product? |
| Parent company | Is the record a brand, subsidiary, or legal entity? |
| Existing website | Does it redirect to the candidate domain? |
When the evidence conflicts, leave the record unresolved. Taking the first array item creates a clean-looking dataset with hidden identity errors.
What error handling does an integration need?
Set a request timeout and handle authentication, rate-limit, server, and network responses separately. Retry short-lived failures with a cap and delay. Do not retry an invalid key or malformed request in a loop.
An empty array is not the same as a failed request. It means the service returned no candidate for the query. Preserve that distinction in logs and user messages.
How should the matched domain and logo be stored?
Store the submitted name, matched name, domain, logo URL, review status, and review date. Cache accepted matches inside the workflow to avoid repeated requests, but allow later refreshes because companies rebrand and change domains.
Use the bulk company logo finder when a person needs to review many names visually. The company enrichment API guide covers the same identity fields inside a wider data-import workflow.
Who is the company identity API for?
CRM and revenue operations
Resolve imported company names to domains before deduplication, routing, and enrichment.
Product teams
Add a reviewed company identity and logo to onboarding, directories, or account interfaces.
Data engineers
Process queued names with explicit authentication, retries, match review, and provenance fields.
Why use this company identity workflow?
Manual and API paths
Test names in the bulk finder, then move repeatable server work to JSON requests.
Candidate-aware guidance
The page treats multiple matches as a review case rather than silently taking row one.
Credential-safe pattern
Examples keep API access in server-side code and out of public clients.
Bulk logo finder
Review names, domains, and logo previews manually before automating the process.
Open the bulk finderEnrichment integration
See error, timeout, authentication, and data-review rules for a wider pipeline.
Read the enrichment guideFree tool directory
Continue into search, authority, backlink, and website research.
Browse all free toolsWhat do developers ask about the company API?
What fields does the API return?
Candidate objects include the matched company name, official-domain candidate, and associated logo URL when available.
Does the API require authentication?
Yes. Current requests require an issued API key. Keep it in server-side secrets and follow the active account quota and API terms.
Can one company name return several matches?
Yes. Company names are not unique, and the result can contain multiple candidates. Validate the domain before saving a record.
What should an application do with no match?
Treat an empty candidate array as an unresolved identity, not as a substitute for an unrelated company. Let a user revise the query or review the record.
Can the API key be used in browser code?
It should not be exposed in public client-side code. Send the request from a server, protected function, or controlled data job.
Is the interactive company finder the same as the API?
They support the same research task, but the finder is a manual bulk interface while the API returns JSON for authenticated server workflows.
How do I find a domain from a company name?
Send the company name from an authenticated server request, inspect the returned candidates, and validate the selected domain against the company’s identity before saving it. Treat no-match and ambiguous results as records that need review.