Fictura
Billing

RevenueCat webhooks

The billing spine for store purchases: paste one URL into RevenueCat and every App Store and Play Store event flows in.

This is the simplest connection in the product — there's no OAuth and no API key. Your app's unique webhook URL is shown when the app is created and permanently on Dashboard → Setup → Keys & webhook, and under Tools → RevenueCat → Manage. Paste it into RevenueCat (Project settings → Integrations → Webhooks) and you're done; the URL's own token is the credential.

What each event becomes

RevenueCat eventFictura event
INITIAL_PURCHASEtrial_started when the period is a trial, subscription_started otherwise (with is_resubscribe: true after an earlier expiration)
RENEWALtrial_converted for a trial's first paid charge, subscription_renewed otherwise
CANCELLATIONtrial_cancelled during a trial, subscription_cancelled otherwise (access continues until expiry); subscription_refunded when the reason is CUSTOMER_SUPPORT
UNCANCELLATIONsubscription_uncancelled; a pending cancel survey is withdrawn
EXPIRATIONtrial_expired or subscription_expired: the only events that end access
BILLING_ISSUEbilling_issue, with in_grace_period and grace_period_expires_at
REFUND_REVERSEDrefund_reversed
PRICE_INCREASE_CONSENT_REQUIRED / _APPROVEDprice_increase_pending / price_increase_accepted
TEMPORARY_ENTITLEMENT_GRANTentitlement_granted
SUBSCRIPTION_PAUSED, SUBSCRIPTION_EXTENDED, PRODUCT_CHANGE, TRANSFER, NON_RENEWING_PURCHASEsubscription_paused, subscription_extended, subscription_product_changed, subscription_transferred, non_renewing_purchase
TESTwebhook_test, so you can see the webhook works; never counted as revenue

RevenueCat's own words are kept on every event (provider, raw_type, raw_reason), next to the price in USD (price_usd) and in the buyer's currency (price_local, currency). The full list is in the event dictionary, with the names that changed.

The webhook only reports what happens after you connect it. To bring in what you sold before that, see bringing your history with you — it runs beside the webhook, and a sale that arrives both ways is still counted once.

Deliveries are idempotent — each event's id is recorded, so RevenueCat's retries can never double-count revenue. Every event feeds four things at once: the entitlement verdict, net-revenue accounting (after your store commission and tax settings), churn states, and — when a trial cancels — the in-app cancel survey.

Keep your own webhook too

RevenueCat fans out to multiple webhook consumers, so adding Fictura doesn't touch the handler you already run. And Fictura re-emits everything uniformly — Stripe and store events in one shape — through its own outgoing webhook.

On this page