LOloops
Webhooks

Email hard bounced

Sent when an email hard bounces. Hard bounces are persistent delivery failures (for example, a mailbox that does not exist); the email will not be delivered. In Loops, a hard bounce also unsubscribes the contact from your audience, so a contact.unsubscribed event will also be sent. Contains sourceType and the related campaignId, loopId (workflow ID), or transactionalId, plus contactIdentity and email objects.

postWebhookemailHardBounced

Headers

webhook-idstring required

Unique message ID. Use to deduplicate deliveries.

webhook-timestampstring required

Unix timestamp of when the message was sent.

webhook-signaturestring required

HMAC signature for verifying the request. Verify using your endpoint signing secret from the Loops dashboard.

Payload

eventName'email.hardBounced' required
eventTimeinteger required

Unix timestamp in seconds.

webhookSchemaVersion'1.0.0' required
sourceType'loop' | 'campaign' | 'transactional' required

The type of email this event relates to. Workflow emails use loop.

campaignIdstring

The ID of the campaign if sourceType is campaign.

loopIdstring

The ID of the workflow if sourceType is loop.

transactionalIdstring

The ID of the transactional email if sourceType is transactional.

Response

Webhook received successfully. Return any 2xx status code to acknowledge delivery.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.