Source type

RevenueCat Source Configuration

RevenueCat sources receive subscription and purchase lifecycle webhooks and verify the configured Authorization header value.

Direct answer

RevenueCat sends the static Authorization header value configured on the integration. FastHook compares that header with the saved value before accepting the webhook.

REVENUECATPOST, PUT, PATCH, DELETEAuthorization Header ValuePayments
RevenueCat webhooks documentationAll source types
RevenueCat sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.RevenueCatProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLREVENUECATProvider credentialheader authVerify 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.

RevenueCat configuration

Create a RevenueCat source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Authorization Header Value values for provider signature. FastHook uses these settings to validate each RevenueCat delivery before it enters the routing workflow.

Source Type

REVENUECAT

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Authorization Header Value

RevenueCat source config
{
  "type": "REVENUECAT",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "REVENUECAT",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

RevenueCat request contract

FastHook compares the Authorization header with the configured value and does not need to read the raw body for this provider.

POSTPUTPATCHDELETE

RevenueCat headers

Preserve authorization when sending RevenueCat 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.

authorization

Static value or Bearer token configured in RevenueCat.

RevenueCat setup

  1. Create a RevenueCat webhook integration with the FastHook Source URL.
  2. Set an Authorization header value in RevenueCat.
  3. Paste the same value into FastHook; FastHook accepts either the exact value or Bearer value form.

Continue with RevenueCat