Meta Source Configuration

Meta configuration

Create a Meta source, keep GET and POST enabled, and provide the configured App Secret, Verify Token values for provider signature. FastHook uses these settings to validate each Meta delivery before it enters the routing workflow.

{
  "type": "META",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "META",
      "webhook_signing_secret": "app-secret",
      "verify_token": "verify-token"
    },
    "allowed_http_methods": ["GET","POST"]
  }
}

GET validation before event POST

1. Meta first calls the FastHook Source URL with a GET validation request.
2. FastHook verifies the configured Meta token or challenge value and returns Meta's expected 2xx response.
3. After validation succeeds, Meta sends normal webhook events as POST requests to the same Source URL.

Meta request contract

FastHook verifies POST deliveries with x-hub-signature-256 and answers GET hub.challenge checks only when hub.verify_token matches.

Special response: GET verification returns the hub.challenge text when mode and verify token are valid.

Meta headers

Preserve x-hub-signature-256, hub.challenge, hub.verify_token when sending Meta 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.

Meta setup

1. Configure the FastHook Source URL as the callback URL in the Meta app dashboard.
2. Set the same Verify Token in Meta and FastHook.
3. Set the App Secret in FastHook so POST deliveries can be verified.

Meta routing hints

• Meta webhook payloads can include Facebook, Instagram, WhatsApp, and Graph API object changes.
• Route by object, field, entry id, or messaging product after GET subscription validation succeeds.

Continue with Meta

• Meta Graph API webhooks documentation
• Source operations and troubleshooting