Monei Connect is for third-party developers building apps on top of Monei. If you’re building your own product directly with Monei APIs, use an API key instead.
When to use Connect
| Use case | Auth method |
|---|---|
| Building your own product with Monei infrastructure | API key |
| Building an app that accesses another user’s Monei account | Monei Connect |
- A budgeting app that reads a user’s Monei transaction history
- A payroll platform that sends Naira from an employer’s Monei wallet to employees
- A DeFi dashboard that executes swaps on behalf of a user
- A savings app that moves funds between a user’s sub-wallets
How it works
Monei Connect follows the standard OAuth 2.0 Authorization Code Flow:Your app redirects the user to Monei
You send the user to
monei.cc/connect/authorize with your client_id, requested scopes, and a state value.User reviews and approves permissions
Monei shows the user a consent screen listing exactly what your app is asking to do. The user can approve all scopes, or only some of them.
Monei redirects back to your app
After approval, Monei redirects to your
redirect_uri with a short-lived code in the query string.Your server exchanges the code for tokens
Your backend makes a server-to-server call to exchange the code for an
access_token and refresh_token. This must happen server-side never in the browser.Key concepts
Scopes: permissions your app requests. Each scope unlocks a specific set of API endpoints. Request only what you need, users are more likely to approve minimal, specific requests. See the full Scopes reference. Partial grants: users control which scopes they approve individually. Your app must handle receiving fewer scopes than it requested. See Handling Partial Grants. Access tokens: short-lived tokens (1 hour) used to call Monei APIs as the user. Prefix:mct_
Refresh tokens: long-lived tokens used to get a new access token without the user re-authorizing. Prefix: mcr_
Client credentials: your app’s identity. client_id is public (mc_). client_secret is secret (mcs_) and only shown once at registration.
What’s different from a regular API key
| API Key | Connect Token | |
|---|---|---|
| Who it represents | You (the developer) | A specific Monei user |
| Scope | Full access to your own account | Only what the user approved |
| User consent required | No | Yes |
| Expiry | Until revoked | 1 hour (refreshable) |
| Use case | Your own product | Third-party access |
Register Your App
Create a developer account and register your app to get credentials
Quickstart
Full working integration in under 10 minutes
Scopes Reference
Every scope, what it unlocks, and which endpoints it covers
OAuth Flow
Deep dive into each step of the authorization flow