Mental model
RaaS Widgets separates your integration surface from the widget runtime:
You never call the Widget API from your servers. You mint links, deliver URLs, and observe results.
Tenancy
Every Partner API call is scoped to yourpartnerId. Your sandbox and production environments, branding, corridors, and allowedFlows are configured by Leap when your account is provisioned. Inspect your profile with GET /partner/me.
Primary objects
Partner
Partner
Your tenant account: environment, branding, allowed flows, corridors, and webhook settings.
Flow
Flow
A productized experience (
smart, m2m, request, …). Each flow has a host URL and a create-link config schema.Magic link
Magic link
A time-bound URL that binds a
referenceId to a flow instance. Response includes linkId, url, token, and expiry.User
User
An end user keyed by your
referenceId (and internal user id). CIP status and history accumulate across links.Operation
Operation
A money-transfer record created when a user completes a transfer in a flow. List and inspect via
/partner/operations.Integration styles
- Minimal — mint
smart(or similar) with onlyreferenceId; the widget collects everything. - Prefill — pass flow
config(for example m2muserData) to skip steps. - Hybrid — prefill what you have; fulfill data requests via webhooks when more is needed.
Next steps
Magic links
Envelope, lifecycle, and delivery.
Flows
Catalog of use cases.