Resolve missing company domains via API
Standardize company website fields from a CRM job, then use confidence, live-domain status, and match reasons to decide what gets written.
Auth
Bearer token
Base URL
https://prospecting.elvesora.com/api
Endpoint
POST /prospecting/company
Output
domain + confidence
Gate
auto-write / review / hold
Implementation console
POST https://prospecting.elvesora.com/api/prospecting/company
Request
- company_name
- Stripe
- additional_context
- US payments infrastructure
Response
- domain
- stripe.com
- confidence
- 95
- is_live
- true
- found
- true
- linkedin_url
- string | null
- industry
- string | null
- sub_industry
- string | null
- sector
- string | null
Decision
- CRM action
- Auto-write website field
- Audit trail
- Store reasons with the update
Ship the cleanup job in four controlled steps
Use the API as a controlled handoff between a CRM record, a domain lookup, a confidence gate, and the system that writes the update.
| Stage | Input | Operation | Output | Owner |
|---|---|---|---|---|
| Trigger | New, updated, imported, or scheduled CRM company record | Send company_name with optional disambiguating context. | A lookup request with a stable payload. | CRM job |
| Lookup | Company name and context | Resolve the official company domain and supporting signals. | domain, confidence, is_live, reasons, lower_reasons, plus nullable LinkedIn and industry context. | Elvesora API |
| Gate | Confidence score and match reasons | Apply the threshold that separates auto-write from review. | Auto-write, review, or hold decision. | RevOps policy |
| Write | Approved domain update | Update the CRM website field or queue the row for review. | Cleaner enrichment, dedupe, routing, and reporting input. | CRM workflow |
API fields your workflow should care about
Keep the implementation small: read the fields that affect write safety, auditability, and usage handling.
| Field | Returned value | Workflow use | Notes |
|---|---|---|---|
domain
|
stripe.com | CRM website field | The official company domain candidate for account identity workflows. |
confidence
|
95 | Write threshold | Found matches return 1-100; a completed no-match returns 0. Error responses include no confidence score. |
is_live
|
true | Safety signal | Helps avoid writing domains that do not appear reachable. |
reasons
|
["Official brand match"] | Audit trail | Store why the match was accepted so operators can review later. |
lower_reasons
|
[] | Review signal | Concerns that lower confidence or move a row into review. |
linkedin_url
|
string | null | Optional company context | Company LinkedIn URL when the lookup provider returns one. |
industry / sub_industry / sector
|
string | null | Optional classification | Nullable company classifications that can support downstream routing or enrichment. |
remaining / limit
|
99 / 100 | Usage monitoring | Track allowance before batch jobs or live workflows run out. |
X-Request-Id
|
response header | Request tracing | A valid incoming ID is echoed; otherwise the API generates one. |
error_type / retryable / retry_after
|
lookup_invalid_response / true / 60 | 502 and 503 retry policy | Retry lookup_invalid_response, lookup_timeout, lookup_connection_failed, or lookup_unavailable after 60 seconds. Error responses omit domain, found, and confidence. |
Use it for company-domain resolution, not adjacent jobs
Company Domain Lookup resolves company names to official domains for CRM automation. Keep the boundary visible so teams do not treat the API as an unrelated domain or contact-data product.
Not WHOIS
No registrant, ownership, or domain-history records.
Not domain availability
No domain purchase, registration, or marketplace checks.
Not email finding
No employee inbox discovery or personal contact lookup.
Not a lead database
No prospect lists, people records, or lead-generation inventory.
Connect it where CRM data changes
The same contract works for live record hygiene and historical backfills.
Salesforce Flow / Apex
Resolve domains on Account or Lead create, update, and import before assignment or enrichment logic runs.
HubSpot workflows
Populate company domain properties and route lower-confidence rows into review workflows.
Warehouse and batch jobs
Backfill historical CRM records from CSVs, dbt models, or internal cleanup pipelines.
Choose the next path
Move between implementation, product evaluation, and broader CRM hygiene context without a sales step.
CRM cleanup solution
Fix Missing Company Domains in CRM
Business-facing workflow for deciding which domains to write, review, or hold.
Open SolutionProduct page
Company Domain Lookup
Review the product surface, input expectations, and lookup capabilities.
Explore ProductUse case
CRM Hygiene Workflows
See how domain lookup, enrichment, and validation fit into data-quality programs.
View Use CaseFrequently asked questions
Start the domain cleanup job with one API request
Generate a key, test the endpoint, and ship a confidence-gated cleanup flow into Salesforce, HubSpot, or your internal data pipeline.
Need the business-facing overview first? Open the CRM cleanup solution