Company Name to Domain and Logo API

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 API request be made?

Send a JSON names array containing 1–25 unique company names. No authorization header is required:

curl 'https://tools-api.growthmarketing.ai/v1/company-search' \
  -H 'Content-Type: application/json' \
  --data '{"names":["Example Company"]}'

A successful response wraps the input row, its match status, and its candidates:

{
  "success": true,
  "data": {
    "rows": [
      {
        "query": "Example Company",
        "status": "matched",
        "candidates": [
          {
            "name": "Example Company",
            "domain": "example.com",
            "logoUrl": "https://tools-api.growthmarketing.ai/v1/logo/example.com"
          }
        ]
      }
    ]
  }
}

Batch names instead of sending one request per row. When the service returns HTTP 429, wait for the Retry-After interval rather than retrying in a tight loop.

How should multiple company matches be resolved?

Use evidence already present in the source record:

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 validation, rate-limit, provider, server, and network responses separately. Retry short-lived failures with a cap and delay. Do not retry malformed input 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.