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.
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 app_user_id. The identifier that links a funnel session, a payment, and the user in your product. Every recipe and webhook payload depends on it. Email is not reliable for matching; app_user_id is.
Configure the Registration webhook. Fires when a funnel visitor submits their email. Delivers email, quiz answers, and app_user_id to your endpoint. Verify the HMAC-SHA256 signature on every request before parsing.
Add a Deep Link Button to your success page. Hands users off to your app or website at the end of the funnel, carrying their identifiers in the URL.
Pick a recipe for your stack. Mobile with RevenueCat, mobile with custom backend, web app with signup, or free funnel with deep link.
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.