API reference

RevenueCat webhook receiver

POST /v1/integrations/revenuecat/{tenantId}/{appId} — the endpoint RevenueCat calls; not called by your backend.

POST /v1/integrations/revenuecat/{tenantId}/{appId}

Note: Not called by your backend. RevenueCat calls this endpoint when you set up the optional RevenueCat webhook of the RevenueCat connector.

This is the receiver for webhooks of RevenueCat. RevenueCat calls it with the URL and the Authorization header value that the dashboard shows once when you set up the RevenueCat webhook (no API key; the scheme Bearer is optional). With HMAC signing switched on in RevenueCat, the header X-RevenueCat-Webhook-Signature: t=<unix>,v1=<hex> is checked over the unchanged body (at most 5 minutes old).

Events Limenia acts on

  • TRANSFER: purchases of a banned or suspended user, or of one whose ban ended less than 90 days ago, move to another App User ID. Limenia creates a ban_evasion report with source: system and priority high on each target.
  • CANCELLATION with cancel_reason CUSTOMER_SUPPORT: counted as a refund on the user file.

Everything else, including TEST, is answered 200 without action.

Answers

Status Meaning
200 Processed, already processed or ignored
400 Not an event or over 1 MiB
401 Wrong header or signature
404 Unknown app or no RevenueCat webhook set up
503 Temporary; RevenueCat retries

Setup in RevenueCat

In RevenueCat, add a webhook integration with the URL and the authorization header value from the dashboard (tab Connectors → RevenueCat), send all events or at least TRANSFER and CANCELLATION, choose the environment Production, and switch on HMAC signing if you can. Set RevenueCat’s restore behavior to “Keep with original App User ID”.