Get Stripe connect URL
Changed onInitiates Stripe Connect OAuth for the customer's own Stripe account, with read-only access. Stripe is a connect-only sales source: each paid charge becomes a Purchase event in GET /v1/events (source stripe), and refunds lower or retract it.
One Stripe account can be connected per profile. Connecting a different account to a profile that already has one redirects with error=stripe_profile_has_account.
Flow
- Redirect the user to authUrl.
- After authorization, Stripe returns the browser to Zernio's internal callback.
- Zernio redirects to redirect_url (or the dashboard when omitted).
On success the redirect carries connected=stripe, profileId, accountId and username (the Stripe account name). On failure it carries error, platform=stripe and error_message.
To match a payment to the ad campaign behind it, set zrn, gclid, fbclid or utm_* keys (and optionally landing_url) in the metadata of the Checkout Session, PaymentIntent or subscription.
Request
- Base URLhttps://zernio.com/api
- Auth
- HTTP bearer
- or API key in header X-Connect-Token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Your Zernio profile ID (get from /v1/profiles).
Custom redirect after connection. Must be an absolute http(s) URL or custom app scheme such as myapp://callback; relative and unsafe URLs return 400.
The Stripe connection being reconnected. The callback refuses to write to any other account.
Response
OAuth authorization URL and authenticated state
Changes
- info
endpoint added
- info