Integrations

GetResponse Webhooks: Integration, Events, and Replay

GetResponse webhooks can trigger CRM updates, subscriber workflows, engagement analytics, suppression handling, and internal automations when contacts subscribe, open messages, click links, or change status.

FastHook validates the secret embedded in the webhook URL, stores the original event, routes accepted deliveries, and returns the exact JSON acknowledgement GetResponse requires to stop retrying the request.

GetResponse sends an event POST, FastHook validates the URL secret and queues the delivery, then answers with the required status JSON.

Supported GetResponse webhook events

  • Contact subscribed, copied, moved, rejected, or unsubscribed.
  • Message opened and email or SMS link clicked.
  • Bounced contact removed and contact email changed.
  • Custom field value changed.
  • Contact import finished and custom report status changed.

Authentication and acknowledgement behavior

  • GetResponse sends JSON payloads with HTTP POST.
  • GetResponse does not publish a cryptographic payload-signature scheme for these webhooks.
  • Add a secret query parameter to the webhook URL, for example ?secret=YOUR_SECRET.
  • FastHook compares that value with the configured source secret before queueing the event.
  • Accepted requests receive 200 OK with {"status":"OK"}.

Create a GetResponse source

Create GetResponse source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "GetResponse production",
    "type": "GETRESPONSE",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "GETRESPONSE",
        "webhook_signing_secret": "use-a-long-random-secret",
        "query_parameter_name": "secret"
      },
      "allowed_http_methods": ["POST"]
    }
  }'

Connect GetResponse

  1. Create the source and copy its FastHook Source URL.
  2. Append ?secret=YOUR_SECRET, using the same value saved in the source.
  3. Open Webhooks in GetResponse and choose Create webhook.
  4. Paste the complete URL, select the required events, and set the webhook to active.
  5. Enable batching only if downstream processing supports an array of up to 100 event objects.

Production checklist

  • Use x-webhook-id as the idempotency key; it remains stable across retries.
  • Route with x-webhook-type or the payload type field.
  • Do not place the secret URL in screenshots, public logs, tickets, or browser analytics.
  • Keep processing asynchronous so the initial acknowledgement stays below GetResponse's timeout.
  • Inspect the failed destination attempt before replaying high-volume campaign events.

Related guides