The core problem
Integrations need stable request, response, error, idempotency, and webhook behavior without inventing endpoints, latency, uptime, or SDK support.
Developers
Integrate contact-data workflows with explicit contracts
Use audited API and webhook surfaces for supported contact discovery, verification, and enrichment while keeping blocked developer tooling clearly unavailable.
Recommended products
Email Finder
Implemented, not deployedUse supported name, company, and domain inputs to look for a possible business email, then verify it separately.
View productEmail Verifier
AvailableCheck supported email format, domain, mail-server, and risk signals without promising delivery.
View productDomain Search
Implemented, not deployedFind supported public business contacts and company context associated with a domain.
View productPerson Enrichment
BlockedComplete supported person fields from existing identifiers with explicit confidence, freshness, and provenance.
View productCompany Enrichment
BlockedComplete supported company fields from a known company or domain without inventing unavailable attributes.
View productLinkedIn Enrichment
BlockedUse supported profile identifiers and public professional fields under a governed enrichment contract.
View productTypical workflow
Create scoped access
Create an authorized workspace key through the existing account surface.
Submit a documented request
Use only existing API contracts and supported fields.
Handle every outcome
Treat partial and error states as first-class results.
Observe delivery
Review request or webhook history where the current product exposes it.
Supported inputs and expected outputs
Supported inputs
- Scoped API keyAuthenticate with an authorized key scoped to its workspace and permissions.
- Documented contact inputSend only fields accepted by the existing API contract.
- Request referenceUse supported request and idempotency context where documented.
Expected outputs
- Normalized resultReceive documented success, partial, unavailable, and failure states.
- Confidence and provenanceRetain safe evidence fields when the operation supports them.
- Webhook eventReceive supported events only after webhook configuration and approval.
Data confidence and field provenance
Machine-readable evidence
Confidence and verification states express data evidence, not business scoring.
Safe provenance
Normalized provenance may be returned; provider secrets and raw responses remain excluded.
Product maturity
Developers
Implemented, not deployedAudited API surfaces exist, but live provider execution and some integration capabilities require approval or remain blocked.
Limitations and controls
- No SDK claimNo supported SDK is published.
- No invented protocolGraphQL, WebSocket, and streaming APIs are not claimed.
- No performance promiseNo fabricated latency, uptime, rate limit, or production-availability claim is shown.
Related products
Frequently asked questions
No. SDK availability is currently blocked.
No. Integrations must stay within audited, existing API contracts.
No. Real provider credentials and live candidates remain blocked.
Integrate from verified surfaces
Review the Developers Hub before building
Create a workspace or sign in to manage approved access; blocked tooling remains unavailable.