Skip to main content
Reference material for Company Identify: the full list of request parameters, validation rules, no-match behavior, and error responses. For walk-through examples, see Company Identify and Identifiers.

​
Request parameter reference

ParameterTypeRequiredDescription
domainsstring[]Exactly one identifier type requiredWebsite domains to identify.
professional_network_profile_urlsstring[]Exactly one identifier type requiredCompany profile URLs to identify.
namesstring[]Exactly one identifier type requiredCompany names to identify.
crustdata_company_idsinteger[]Exactly one identifier type requiredCrustdata company IDs to identify.
exact_matchbooleanNoSet to true for strict domain matching.
Current platform behavior: Submit exactly one identifier type per request.
Current platform behavior: exact_match: true enforces strict domain matching, but it can still return multiple matches when more than one company record shares that same domain.
The OpenAPI model currently reuses the Enrich request schema, but this reference documents the live Identify behavior. Use Enrich when you need the broader profile sections.

​
No-match behavior

When no company matches the identifier, current platform behavior returns 200 with an empty matches array: 
[
    {
        "matched_on": "thisdomaindoesnotexist12345xyz.com",
        "match_type": "domain",
        "matches": []
    }
]
The OpenAPI spec also defines a 404 response for Identify. Current platform behavior returns 200 with empty matches, but integrations should handle both.

​
Errors

StatusMeaning
400Invalid request — missing or multiple identifier types, or malformed input.
401Invalid or missing API key.
403Permission denied or endpoint unavailable for your account.
404No data found.
500Internal server error.
400 — Missing identifier
{
    "error": {
        "type": "invalid_request",
        "message": "Exactly one identifier must be provided: crustdata_company_ids, names, domains, or professional_network_profile_urls",
        "metadata": []
    }
}
401 — Invalid API key
{
    "message": "Invalid API key in request"
}

​
API reference summary

DetailValue
EndpointPOST /company/identify
AuthBearer token + x-api-version: 2025-11-01
PricingFree
RequestOne identifier type: domains, names, crustdata_company_ids, or professional_network_profile_urls. Optional: exact_match.
Response[{ "matched_on", "match_type", "matches": [{ "confidence_score", "company_data" }] }]
Errors400 (bad request), 401 (bad auth), 403 (permission), 404 (no match), 500 (server error)
See the full API reference for the complete OpenAPI schema.