Source type

GoTo Webinar Source Configuration

GoTo Webinar sources answer callback URL validation and receive registrant, webinar, attendance, and survey events with timestamped HMAC verification.

GOTO_WEBINARGET, POSTWebhook Secret KeyCommunication
GoTo Webinar webhook implementation guideAll source types
GoTo Webinar sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.GoTo WebinarProviderGET, POSTSetup + eventsFastHookSource URLGOTO_WEBINARProvider credentialchallengeVerify 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

GoTo Webinar configuration

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

Source Type

GOTO_WEBINAR

Allowed methods

GET, POST

Authentication

Provider signature

Credential fields

Webhook Secret Key

GoTo Webinar source config
{
  "type": "GOTO_WEBINAR",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "GOTO_WEBINAR",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["GET","POST"]
  }
}

Callback URL validation before events

  1. GoTo validates the configured callback URL with a GET request.
  2. FastHook returns an empty 200 OK response so the callback URL can be registered.
  3. After the webhook and user subscription are active, GoTo sends timestamped, signed event POST requests.

GoTo Webinar request contract

FastHook verifies the base64 HMAC-SHA256 digest of timestamp:raw-body and rejects timestamps outside the configured tolerance.

GETPOST

Special response: Callback validation GET requests receive an empty 200 OK response.

GoTo Webinar headers

Preserve x-webhook-signature, x-webhook-signature-timestamp, x-webhook-secretkey-id, x-webhook-signature-version when sending GoTo Webinar 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-signature

Base64 HMAC-SHA256 signature.

x-webhook-signature-timestamp

Millisecond timestamp prepended to the raw body with a colon.

x-webhook-secretkey-id

Identifier of the GoTo webhook secret key used to sign the event.

x-webhook-signature-version

GoTo signature format version.

GoTo Webinar setup

  1. Create a GoTo Webinar developer app and webhook secret key.
  2. Use the FastHook Source URL as the callback URL; FastHook returns 200 OK to GoTo's validation GET.
  3. Create and activate one webhook per event, then create the required user subscriptions.
  4. Copy the GoTo webhook secret key value into FastHook before activating deliveries.

GoTo Webinar routing hints

  • GoTo Webinar callbacks usually route by eventName, webinarKey, sessionKey, or registrantKey.
  • Use eventKey as the delivery-level idempotency key when downstream workflows can create side effects.

Continue with GoTo Webinar