Integrations

RevenueCat Webhooks Guide

RevenueCat webhooks send subscription and purchase lifecycle events into your backend. Those events often update entitlements, customer status, support automation, analytics, and billing operations, so failures need a clear trail from provider delivery to destination processing.

FastHook gives RevenueCat a stable source URL, verifies the configured Authorization header value, stores request evidence, routes accepted lifecycle events to destinations, and keeps retries and replay close to the failed delivery record.

Provider event routing topology for RevenueCat subscription webhooks.
Route subscription lifecycle traffic by ownership. Entitlements, analytics, support, and finance often need different recovery paths.

RevenueCat Authorization header

RevenueCat lets you configure an Authorization header for webhook deliveries. In FastHook, create a RevenueCat source and paste the same value into Authorization Header Value. FastHook accepts either the exact saved value or the Bearer form of that value.

  • Authorization: Bearer revenuecat-token works when the saved value is revenuecat-token.
  • Authorization: revenuecat-token also works when you save the exact header value.
  • Use different header values for production and sandbox RevenueCat projects.

Create a RevenueCat source

Create RevenueCat source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "RevenueCat production",
    "type": "REVENUECAT",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "REVENUECAT",
        "webhook_signing_secret": "revenuecat-token"
      },
      "allowed_http_methods": ["POST", "PUT", "PATCH", "DELETE"]
    }
  }'

Subscription event routing

Keep RevenueCat routing explicit. Subscription lifecycle events may look similar at ingress, but they often belong to different downstream systems and recovery policies.

NeedDestination patternFailure concern
Entitlement updatesAccount or access serviceDuplicate grants, stale access, missed revocation
Lifecycle analyticsWarehouse or event streamGaps after receiver downtime
Support automationCRM or helpdesk workflowDuplicate tickets and noisy retries
Finance reviewSheet, warehouse, or reconciliation endpointReplay windows without idempotency

Debugging RevenueCat webhooks

  • No request appears: confirm the RevenueCat webhook URL is the generated FastHook Source URL.
  • 401 source auth failed: compare the configured FastHook value with the RevenueCat Authorization header.
  • Provider retries continue: inspect the destination attempt response before replaying more events.
  • Entitlements drift: add receiver-side idempotency before applying subscription side effects.
  • Sandbox traffic leaks into production: split RevenueCat sources by environment.

Official RevenueCat docs

Related guides