Developer Quickstart

For backend engineers wiring Zellify into their product. You'll have a verified Registration webhook, a working Deep Link Button on the success page, and a clear path to granting access after payment. You need a Zellify account, an HTTPS endpoint, and the web funnel configured.

Using Claude Code? Skip the manual steps. The Zellify MCP does this whole quickstart for you: detects your stack, generates a webhook handler against your real funnel schema, and verifies the round trip. Run /integrationcheck and review the plan.

Before you start#

Read app_user_id once. Every recipe, webhook payload, and metadata field depends on it.

1. Read app_user_id#

Open the app_user_id concept page. This is the identifier that links a funnel session to a payment and to the user in your system. It appears in three places: the Registration webhook payload, your payment provider's metadata, and the Deep Link Button URL at the success page. Email is not reliable for matching; app_user_id is.

2. Configure the Registration webhook#

This webhook fires when a user submits their email in your funnel, delivering their quiz answers, email, and app_user_id to your backend.

Open Dashboard → Settings → Developers and add your endpoint URL. Copy the webhook secret.

Verify signatures on every request before parsing the body:

See Registration webhook for the full payload.

The Deep Link Button hands the user off to your app or website at the end of the funnel, carrying their identifiers in the URL.

Drop a Deep Link Button component onto the success page in the funnel builder. Configure the URL template with the variables you need: {{email}}, {{app_user_id}}, and any payment provider IDs. The button opens the deep link on mobile and redirects on web. See Deep Link Button.

4. Pick a recipe#

Mobile app with RevenueCat
RevenueCat handles entitlement state.
Mobile app with custom backend
You own subscription logic.
Web app with signup page
Web product, post-payment signup.
Free funnel with deep link
No payment, just routing.
Payment events
Which Stripe, Paddle, or Solidgate events to listen to per scenario.
Checkout metadata
Every field Zellify attaches, per provider.