Real-Time Events via Webhooks

Webhooks give your engineering team a real-time event stream from Supapitch, enabling custom integrations that react the instant something happens — an email is sent, a prospect opens it, a reply comes in, a message bounces, or a campaign completes. Instead of polling the REST API on a schedule and checking for changes, your systems receive an HTTP POST request with a structured JSON payload the moment the event fires. This push-based architecture means lower latency, less wasted compute, and simpler integration code compared to poll-based approaches.

Supapitch supports webhook subscriptions for all major outreach events: email.sent, email.opened, email.clicked, email.bounced, email.replied, reply.categorized, campaign.completed, recipient.added, and recipient.unsubscribed. Each event payload includes a consistent JSON structure with the event type, timestamp, and relevant entity data — for example, a reply event includes the recipient's email address, the campaign ID, the reply body, and the AI-categorized intent. Your engineering team can use these payloads to update internal databases, trigger downstream workflows, populate analytics pipelines, or fire alerts in real time.

Security is built into every webhook delivery. Each request includes an X-Supapitch-Signature header containing an HMAC-SHA256 hash computed from the payload body and your webhook secret. Your receiving endpoint should verify this signature before processing the payload to ensure it genuinely originated from Supapitch and was not tampered with in transit. The webhook secret is generated when you create an endpoint and can be rotated at any time from the Supapitch dashboard. All webhook requests are sent over HTTPS, so payload data is encrypted in transit.

If your endpoint is temporarily unreachable — due to a deployment, network issue, or service outage — Supapitch retries failed deliveries with exponential backoff. The first retry happens after 30 seconds, the second after two minutes, then five minutes, fifteen minutes, and so on, continuing for up to 24 hours. Every delivery attempt is logged in the Supapitch dashboard with the HTTP status code your endpoint returned, the response body, and the time of the attempt. This delivery log is invaluable for debugging integration issues because you can inspect the exact payload Supapitch sent and the exact response your server returned without needing to reproduce the event in production.

Register endpoints and select event subscriptions from the Supapitch settings page — no code deployment is needed for configuration changes. You can create multiple endpoints and route different event types to different URLs, making it easy to separate concerns in your architecture. For example, route reply events to your CRM integration service, bounce events to your data quality pipeline, and all events to a centralized analytics ingestion endpoint. Each endpoint can subscribe to any combination of event types, and you can update subscriptions at any time without re-registering the endpoint.

For teams getting started with webhooks, Supapitch provides a built-in test mode that sends sample payloads to your endpoint so you can verify your integration logic before going live. You can also replay historical events from the delivery log, which is useful during development and when recovering from endpoint downtime. If your team uses serverless functions on platforms like AWS Lambda, Google Cloud Functions, or Vercel, webhooks integrate naturally — each event triggers a function invocation with the payload as input, requiring minimal infrastructure management on your end.