Evercontact · AsyncAPI Specification

Evercontact Webhooks

Version

View Spec View on GitHub CompanyContact ManagementContact DataData EnrichmentEmailSignature ParsingData ExtractionCRMAsyncAPIWebhooksEvents

AsyncAPI Specification

evercontact-webhooks.yml Raw ↑
generated: '2026-08-14'
method: searched
source: https://www.evercontact.com/api.html
type: Webhooks
summary: >-
  Evercontact delivers real-time relationship changes over webhooks. Consumers
  register subscription endpoints via POST /v1/webhooks and receive event
  callbacks; the same changes are also available as a paginated pull stream via
  GET /v1/events. No AsyncAPI document is published by the provider, so this
  captures the documented webhook catalog only (never fabricated).
registration:
  operation: POST /v1/webhooks
  base_url: https://api.evercontact.com
pull_stream:
  operation: GET /v1/events
  paginated: true
events:
- name: contact.created
  description: A new canonical person record was created from a parsed signature.
- name: contact.updated
  description: An existing person record was enriched or changed.
- name: company.linked
  description: A contact was associated with a resolved company/organization record.
undocumented_events_observed:
- name: intro.sent
  source: https://www.evercontact.com/index.html
  note: >-
    Appears in the "Email intelligence" illustration on the homepage with the shape
    {event, from, to[], type, conf} and type "warm_intro". It is NOT in the
    documented event list on api.html, so the real event taxonomy is larger than
    the three names published. Recorded as an observation, not as a supported event.
asyncapi_document: null
delivery:
  retries: not published
  signing: not published
  ordering: not published
  replay: 'GET /v1/events (paginated pull) is the documented catch-up mechanism'
notes: >-
  Payload schemas, delivery retry policy, signature verification and event ordering
  are not published on the public docs page; only the event names and the delivery
  model are documented. No AsyncAPI document is served on any Evercontact host
  (probed 2026-08-14). The registration and pull operations could not be exercised:
  api.evercontact.com fails TLS and returns 403 - see
  well-known/evercontact-well-known.yml.
checked: '2026-08-14'