Menu

Developers

Hook Zellify into your own code. Zellify does not ship a REST API or SDK today. What you get is a well-documented webhook for lead capture, a clear metadata contract on every checkout, and a recipe book for the common jobs: grant app access after a payment, pair a funnel session with a user in your system, route free-funnel users into your product.

Skip ahead with Claude Code#

Use the Zellify MCP: If you use Claude Code, the Zellify MCP reads your funnel schema, picks the right recipe for your stack, and writes the webhook handler in one session. Two install commands and a /integrationcheck is the fastest path through everything below.

Read these first#

app_user_id
The identifier that links a funnel session, a payment, and the user in your product.
Deep Link Button
How the success page routes users into web or mobile apps.
Checkout metadata
What Zellify attaches to Stripe, Paddle, and Solidgate objects.

Webhooks#

Webhooks overview
Delivery guarantees, signature verification, what Zellify sends.
Registration webhook
Fires when a funnel visitor submits their email.

Recipes#

Mobile app with RevenueCat
Grant entitlements via RevenueCat after a web funnel pays.
Mobile app with custom backend
Own your subscription logic. Listen to Stripe or Paddle events directly.
Web app with signup page
Route paid web-funnel users into a web product.
Using existing webhooks
Additive changes for teams already running a Stripe or Paddle handler.
Early account creation
Pair the Registration webhook with payment events.
Free funnel with deep link
No payment, just routing leads into your product.
Custom registration component
Call your backend from the success page with a React component.

What Zellify does not do#

No API. No SDK. No entitlement management. Zellify exposes webhooks and a metadata contract on every checkout. It does not expose a REST API, ship client SDKs, or manage entitlements in your app. Granting access after a payment is your responsibility, and the guides above cover the patterns that work.