RevenueCat runs the purchase. Amba runs what happens next.

The RevenueCat integration syncs subscription state into Amba server-side. RevenueCat validates purchases and sends webhook events; Amba turns them into entitlements your app reads with one SDK call, neutral subscription properties, live segments, and push targeting. Amba configures and composes with RevenueCat — it never replaces it, and billing truth stays where it is.

This page is for the moment mid-build when subscriptions work in RevenueCat and the next question is "now what do I do with a subscriber?" The answer this integration ships: every purchase, renewal, cancellation, and expiration RevenueCat observes becomes server-side state in Amba — an entitlement your app gates features on, subscription properties segments filter by, and events that can trigger rewards and push. You write no webhook handler, host no server, and parse no receipts. The setup below is the whole shipped surface, verified against the live pipeline; the step-by-step depth lives in the docs, linked throughout.

Verified against the shipped webhook pipeline, June 2026. Every fresh event also updates the neutral subscription_* user properties; redeliveries dedupe on the event ID, and an ordering watermark stops a stale event from overwriting newer state.

1. 01

   Configure the integration

   Call amba_integrations_configure with provider "revenuecat" and your secret REST API key (not the publishable SDK key) plus a webhook_secret you choose. The response includes the exact webhook_url for your project. Keys are stored server-side and never returned to a client.

   One tool call — returns your webhook URL

   copy

   amba_integrations_configure
     { "project_id": "proj_…", "provider": "revenuecat",
       "config": { "secret_api_key": "<RevenueCat secret API key>",
                   "webhook_secret": "<long random string you generate>" } }
     → { …integration, "webhook_url":
         "https://api.amba.dev/webhooks/revenuecat?project_id=proj_…" }

2. 02

   Register the webhook in RevenueCat

   Paste the returned webhook_url into your RevenueCat project's webhook settings, and set the webhook's Authorization header value to `Bearer <webhook_secret>` — the literal word Bearer, a space, then the secret. Amba compares the full header on every delivery and rejects anything that does not match.

3. 03

   Declare the entitlement contract

   Define the entitlement your app gates on and the products that grant it. Features check the entitlement, never a product or a store — so you can change how it is sold without touching app code.

   Entitlement + product map — real tools, schema-true arguments

   copy

   amba_entitlements_define
     { "project_id": "proj_…", "key": "pro", "display_name": "Pro" }
   
   amba_products_create
     { "project_id": "proj_…", "product_id": "pro_yearly",
       "grants_entitlement_id": "pro",
       "store_product_refs": { "app_store": "com.yourapp.pro.yearly",
                               "play_store": "pro-yearly" } }

   amba_entitlements_map_product adds extra entitlements to a product (bundles). The webhook union-joins the entitlements RevenueCat sends with the ones this map declares.

4. 04

   Test the connection and gate a feature

   amba_integrations_test verifies the stored credential can reach RevenueCat. In the app, read entitlement state with one SDK call — no receipt parsing client-side.

5. 05

   Wire the activation loop

   Create a segment on the synced subscription properties, point a push campaign at it, and optionally bind a reward rule to entitlement.granted. From here, subscription state drives engagement automatically.

   Segments + push from subscription state

   copy

   amba_segments_create
     { "project_id": "proj_…", "name": "Active subscribers",
       "rules": { "operator": "AND", "conditions": [
         { "field": "properties.subscription_active", "op": "eq", "value": true }
       ] } }
   
   amba_push_campaigns_create
     { "project_id": "proj_…", "name": "Pro welcome",
       "title": "You're in", "body": "Pro is live on this device.",
       "segment_id": "<segment id from the previous call>" }