The Qwik Partner API
The Partner API exposes Qwik's card, banking, and money-movement platform to your business behind a single, clean REST surface, authenticated with an API key. Qwik runs the card + banking platform on top of regulated providers. Qwik is the abstraction layer.
Using this documentation anyone can integrate Qwik's features into their own product. Every endpoint, header, request body, and response shape is taken directly from the backend implementation.
What you can do
- Register and authenticate your own users - each gets a Qwik-managed identity isolated to your organization.
- Onboard users for a card - KYC, underwriting, and agreement acceptance via a hosted embed.
- Manage cards - fetch details, freeze/unfreeze, render the card image, surface credit insights.
- Move money - link an external bank, pull funds in (deposits), push funds out (withdrawals).
- Read transactions - and re-categorize them.
- File and track disputes.
- Receive webhooks - for everything asynchronous (ACH settling, transactions posting, cards freezing).
Your data is isolated: every user, card, transaction, and webhook you create is scoped to your partner_id and is never visible to another partner or to the Qwik consumer app.
Two kinds of caller
The API has two authentication layers because two different actors call it:
| Caller | Example actions | Auth |
|---|---|---|
| Your backend (the organization) | Register a user, manage webhooks, view org config | API key + secret |
| An end user (acting through your app) | Onboard for a card, deposit money, view transactions | API key + secret plus a user session token |
Both are covered in Authentication.