Integration status
Eighteen audited capabilities have code, route, test, or contract evidence. Sandbox, Swagger, Postman Collection, and SDK remain blocked.
Developers
Build from audited integration surfaces
Review authentication, request lifecycle, results, idempotency, webhooks, security guidance, and capability maturity without invented SDKs or endpoints.
Integration surfaces and controls
Integration surfaces
Existing REST-style JSON routes cover selected contact-data and workspace workflows; this hub does not add endpoints.
Authentication overview
Existing API-key controls bind access to authorized account and workspace scope.
Request lifecycle
Requests pass authentication, scope, input, policy, and operation checks before a normalized response.
Response and error model
Integrations must handle success, partial, unavailable, invalid, unauthorized, limited, and safe internal-error outcomes.
Idempotency
Supported write operations use existing idempotency controls; callers must follow the documented contract.
Webhooks
Webhook configuration, signing, delivery history, and retries remain governed by current permissions and maturity.
Testing and mock
Internal mock-provider execution is isolated and zero-live; no public sandbox is available.
Security guidance
Keep keys server-side, apply least privilege, rotate access, verify webhook signatures, and never expose credentials in client code.
Product maturity
A route or class does not prove live availability. Use the capability status before planning an integration.
Developer capability matrix
Status is limited to Available, Implemented Not Deployed, Approval Required, or Blocked.
- API key authentication Available
- Existing API v1 requests authenticate with stored, revocable keys.
- Workspace scope Available
- Supported keys and operations are checked against workspace ownership and permissions.
- Request identifiers Available
- Existing API responses expose safe request context for support and audit.
- JSON responses Available
- Existing API v1 controllers return structured JSON contracts.
- Safe error envelope Available
- Existing API failures use normalized codes and messages rather than raw provider errors.
- Idempotency controls Available
- Existing supported writes can prevent duplicate processing under the documented contract.
- Webhook configuration Approval required
- Workspace webhook configuration exists but may require approval.
- Webhook signatures Approval required
- Existing delivery logic supports signed webhook verification controls.
- Webhook delivery history Approval required
- Existing workspace surfaces retain delivery status for permitted review.
- Email Finder API Implemented, not deployed
- An existing normalized endpoint is implemented; live provider execution remains blocked.
- Email Verifier API Available
- Existing verification behavior is available within its documented evidence limits.
- Domain Search API Implemented, not deployed
- An existing endpoint is implemented; coverage and live-provider availability remain constrained.
- Contact read API Available
- Existing authenticated contact retrieval applies visibility and reveal controls.
- Contact reveal API Approval required
- Existing reveal behavior requires workspace, permission, and commercial approval controls.
- Contact Lists API Available
- Existing list operations organize workspace-owned contact records.
- Saved Searches API Available
- Existing saved-search routes retain queries and run them against permitted current data.
- Enrichment Jobs API Implemented, not deployed
- Existing job endpoints are implemented but live contact-job rollout remains blocked.
- Machine-readable schema Available
- An existing JSON schema route documents audited API contracts.
- Sandbox Blocked
- No audited public sandbox implementation is available.
- Swagger Blocked
- No audited Swagger interface is available.
- Postman Collection Blocked
- No audited Postman collection is available.
- SDK Blocked
- No audited supported SDK is available.
Existing documentation links
These links point to existing product surfaces. Authentication and maturity controls still apply.
Start with governed access
Create a workspace or sign in
Use existing account controls to manage approved access; this hub does not enable blocked developer capabilities.