Rheo documentation
Developer Guide

Overview

Connect attribution, monetization, and host-rendered surfaces to flows while your app keeps API keys and native modules.

Integrations and canvas surface nodes let the dashboard and SDK orchestrate third-party surfaces, signals, and host-owned UI. Rheo does not replace your vendor SDKs: you still configure RevenueCat, Superwall, and AppsFlyer (or equivalents) in app startup when you use those providers. Stripe Integration Nodes store a Payment Link URL. The web SDK redirects, and Rheo records the purchase only after Stripe sends checkout.session.completed to the app webhook. Rheo stores the webhook signing secret, not a Stripe API key. External Surface Nodes (headless) skip vendor toggles — you register a component in the host app keyed by the canvas node id.

How integrations show up in the product

Dashboard: App settings → Integrations — RevenueCat, Superwall, and AppsFlyer toggles.

  • App settings → Integrations — Per-app toggles for Stripe, RevenueCat, Superwall, and AppsFlyer. Turn a paywall integration on and the webhook fields in that section stay visible, so you can copy the URL, save the write-only secret, and choose which stores count that provider's charges. One provider can count charges for each store. App Store and Play are RevenueCat or Superwall. Web can also be Stripe. Allowed browser origins live on App settings → SDK. Disabled providers block publish when a flow still references them. External Surface Nodes do not use this panel.

Partner webhook URL shape

When an integration is enabled, the dashboard shows a per-app HTTPS webhook URL in this shape (paste it into the partner dashboard with the signing secret Rheo shows once):

https://api.getrheo.io/v1/public/{stripe|revenuecat|superwall}/apps/:appId/webhook

Replace the host if you self-host the API. See Stripe, RevenueCat, and Superwall.

  • Flow builder — Separate add-menu items: Integration Node (Stripe, RevenueCat, or Superwall when that integration is enabled in App Settings) and External Surface Node (headless host UI), plus decision nodes (branch on sdk.* including normalized attribution and paywall outcome keys). Pinning a version warns (non-blocking) when the manifest includes mobile-only or web-only steps. Experiment assignment shows the same warning.