Find Company Candidates by Website Domain

View all Crunchbase Company & Investment Data endpoints →

Resolve a website domain or company website URL into candidate Crunchbase organizations. The required domain string accepts a value such as stripe.com or a website URL. This is a candidate lookup, not a guaranteed one-domain-to-one-company mapping; no pagination or result-limit parameter is documented. An observed successful probe for stripe.com returned an object with domain, total_count of 4 and an items array containing stripe, stripe-capital, stripe-841c and stripe-atlas. The probe metadata confirms that the primary Stripe record had the expected UUID, website, founders and business description. It does not establish that the first item is always the correct match or that every domain will resolve. Separately, the truncated documented response example illustrates item identity fields id, uuid, name, link, image, website, aliases and short_description; categories and category_groups as id/name lists; and location with city, continent, country, region, groups and ids. Founders are illustrated with id, uuid, name, type and link, while investors is also present. Other illustrated fields cover employee_count; acquirer; operating_status and ipo_status; founded_on, closed_on, delisted_on and went_public_on; funding_stage, funding_total, equity_funding_total, last_funding_at and last_funding_type; investor_stage and investor_type; contacts_count, investments_count, exits_count and diversity_spotlight_investments_count; growth_score, heat_score, rank, rank_company and rank_delta_90d; and revenue_range, stock_exchange and stock_symbol. This extended field inventory is source-example evidence, not a field-by-field live guarantee. Financial totals, dates and several status or investor fields are null in the illustrated record. Compare candidate identity, description, website and relationships before confirming a CRM mapping. Store the input domain, candidate identifiers and confirmed organization separately. Missing financial data is unknown rather than zero, and this endpoint does not promise domain ownership verification, exhaustive coverage or current financial figures.

API Features

Website-to-organization candidate lookup Supply a domain or company website URL through the single required domain parameter to request candidate organizations.
Multiple-match domain review The observed stripe.com probe returned four candidates, demonstrating why a shared domain must not automatically select or merge the first organization.
Company identity cross-checks Compare returned company IDs and UUIDs with website, founders and business description; those profile details were confirmed for the primary Stripe record in the supplied probe metadata.
Source-documented enrichment context The separate source example illustrates categories, locations, workforce, funding and ranking fields for candidate review, with nullable values and no field-by-field completeness guarantee.

Live API Demo

GET /api/project/crunchbase/company-by-domain

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/crunchbase/company-by-domain?key=<API_KEY>&domain=stripe.com'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Should domain contain a bare domain or a complete URL?

The required domain parameter is documented to accept a website domain, such as stripe.com, or a company website URL. The supplied live evidence covers stripe.com only; URL normalization and path handling have not been separately verified.

Can one domain return several Crunchbase organizations?

Yes. The successful stripe.com probe returned total_count of 4 with candidate IDs stripe, stripe-capital, stripe-841c and stripe-atlas. Do not assume a domain identifies exactly one organization or that item order determines the best match.

Which response fields were actually observed?

The probe metadata confirms the domain, total_count and four-item candidate list for stripe.com, plus the expected UUID, website, founders and business description on the primary Stripe record. The broader profile-field inventory is from a separate truncated source example and is not independently verified field by field.

How should I choose a candidate for CRM enrichment?

Compare company identity, website, description and founders or other available relationships before confirming the mapping. Store the input domain, candidate IDs, chosen company ID and UUID, and reviewer decision separately. A shared website alone is not sufficient evidence to merge accounts.

Are funding amounts, dates and company status guaranteed?

No. The documented example contains null financial totals, dates and several status or investor fields. Treat those values as unknown, not zero or proof of inactivity. Current values and complete coverage are not established by the supplied evidence.

Can I paginate matches or use this as proof of domain ownership?

No pagination or limit parameter is documented for this operation. The response is a set of company candidates associated with the submitted website, not a domain-ownership verification result or a guarantee that every matching organization has been found.

Related operations

Guides

View Subscription Plans →