Send contact events to your systems as they happen

Subscribe your application to the OpenContact events it needs. Each delivery is signed, carries a stable identifier, and retries when a temporary endpoint failure occurs.

Connect your endpoint · Read the webhook guide

Receive notifications when a contact is created, changes status, unsubscribes, bounces, or complains. Configure subscriptions in the dashboard or through the API.

One project can send events to the systems that need them without exposing unrelated workspace data.

Verify every delivery

OpenContact signs the raw request body with HMAC-SHA256 and includes the timestamp in the signature header. Your endpoint can reject altered requests and enforce a time window to reduce replay risk.

The signing secret is shown when the subscription is created. Rotate it from the dashboard when needed.

Process retries safely

Every event has a stable delivery ID in the body and request headers. Store it and ignore an ID that has already been processed.

When an endpoint returns a non-success response, OpenContact retries with exponential backoff so a brief outage does not immediately discard the event.

Test before live traffic

Send a sample event from the dashboard to check routing and signature verification. Recent delivery status and response codes make endpoint failures visible without digging through server logs first.

Common workflows

mirror contact status into your application database;
begin onboarding when a lead is created;
update an internal suppression table immediately;
feed an analytics or warehouse pipeline;
notify an operational workflow when a contact changes.

Next steps

Explore the Developer API · See activity reporting · Read the webhook contract