Source type

GetResponse Source Configuration

GetResponse sources receive contact, email engagement, import, and report events, validate a secret query parameter, and return GetResponse's required JSON acknowledgement.

GETRESPONSEPOSTWebhook URL SecretEmail and messaging
GetResponse webhook documentationAll source types
GetResponse sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.GetResponseProviderPOSTSetup + eventsFastHookSource URLGETRESPONSEProvider credentialPING/204Verify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.Provider setupValidate firstSetup challenge

GetResponse configuration

Create a GetResponse source, keep POST enabled, and provide the configured Webhook URL Secret values for provider signature. FastHook uses these settings to validate each GetResponse delivery before it enters the routing workflow.

Source Type

GETRESPONSE

Allowed methods

POST

Authentication

Provider signature

Credential fields

Webhook URL Secret

GetResponse source config
{
  "type": "GETRESPONSE",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "GETRESPONSE",
      "webhook_signing_secret": "long-random-url-secret",
      "query_parameter_name": "secret"
    },
    "allowed_http_methods": ["POST"]
  }
}

GetResponse request contract

GetResponse does not publish a payload-signature scheme. FastHook compares the configured secret with the secret query parameter before queueing the request.

POST

Special response: Accepted deliveries receive 200 OK with the JSON body {"status":"OK"}, preventing unnecessary GetResponse retries.

GetResponse headers

Preserve x-webhook-type, x-webhook-id, x-request-id when sending GetResponse test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-webhook-type

Event type, matching the payload type field.

x-webhook-id

Stable event UUID across delivery retries, useful for idempotency.

x-request-id

Unique UUID for an individual delivery attempt.

GetResponse setup

  1. Create a GetResponse source and choose a strong Webhook URL Secret.
  2. In GetResponse, create a webhook and append ?secret=YOUR_SECRET to the generated FastHook Source URL.
  3. Select the contact, message, import, or report events required by the workflow.
  4. Enable batching only when the receiver is prepared for an array containing up to 100 events.

GetResponse routing hints

  • GetResponse events usually route by x-webhook-type or the payload type field, then by campaign, contact, or message identifiers.
  • Use x-webhook-id as the idempotency key because it remains stable when GetResponse retries an event.

Continue with GetResponse