Source type

Meta Source

Meta sources receive Facebook, Instagram, WhatsApp, and Graph API webhook notifications and answer the subscription verification challenge.

METAGET, POSTApp SecretCommunication
Meta Graph API webhooks documentationAll source types
Meta sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.MetaProviderGET, POSTChallengeFastHookSource URLMETAProvider 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 setupSpecial responsechallenge
FastHook keeps the provider-facing contract on the source. Accepted requests are stored before routing, while rejected requests keep enough evidence to debug signature, method, and challenge failures.

When to use this source type

Choose the META source type when Meta is the system sending webhook requests into FastHook. The source type keeps sender-specific setup close to the source: accepted methods, verification headers, challenge handling, and the exact credential fields are documented together so operators do not need to translate a generic HMAC form into a provider-specific contract.

FastHook verifies the source before accepted traffic is queued. A valid request is stored with verified: true, then connections route it to destinations. A bad signature, wrong token, or missing provider header is rejected as SOURCE_AUTH_FAILED. A method outside the allowed set is rejected as SOURCE_METHOD_NOT_ALLOWED.

FastHook configuration

In the dashboard, create a source, set Source Type to Meta, keep Authenticate enabled when verification is required, and fill the fields below.

Source Type

META

Allowed methods

GET, POST

Authentication

Provider signature

App Secret

Copy this value from Meta and store it on the FastHook source.

Verify Token

Copy this value from Meta and store it on the FastHook source.

{
  "type": "META",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "META"
    },
    "allowed_http_methods": ["GET","POST"]
  }
}

HTTP methods

This source accepts only the methods listed below. Keep the set narrow so provider mistakes and accidental test calls are visible as rejected requests instead of being silently accepted.

GETPOST

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

Headers and verification

FastHook verifies the provider-specific values below before the request is accepted. The comparison is done against the raw inbound request body or the exact provider-specific signing input described here.

x-hub-signature-256

HMAC-SHA256 signature with sha256= prefix.

hub.challenge

GET query value FastHook echoes during subscription verification.

hub.verify_token

GET query value FastHook compares with the configured verify token.

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

Provider setup checklist

  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.
  4. Open Meta Graph API webhooks documentation when you need the provider's event list, dashboard steps, or retry policy.

Troubleshooting

  • No request appears: the provider is not calling the generated FastHook Source URL, the source URL was copied before saving, or the provider has not completed its setup validation.
  • 405 method rejected: the provider sent a method outside GET, POST. Edit the source only if the provider documentation says that method is expected.
  • 401 source auth failed: check the configured FastHook field, the provider signing secret, and the header names listed on this page.
  • Signature mismatch: make sure the provider signs the same public Source URL it calls and that no proxy, parser, or manual resend changed the raw request body before FastHook received it.

Related docs