API Reference
Migo Payments exposes four REST APIs, each rendered below with Scalar (interactive — try endpoints directly from the browser).
Which API do I need?
| API | You want to… | Base URL |
|---|---|---|
| Wallet Gateway | Build a wallet or card program — issue cards, tokenize, charge, transfer, onboard merchants | https://api.ali.app/rest |
| Middleware | Issue hosted Payment Links, run subscription billing, accept alternative payments, manage fraud suspensions | https://mw.migopayments.com |
| CMS Backoffice | Operate a partner backoffice — manage cardholders, permissions, bulk uploads | https://api.ali.app/cms/rest |
| Migo Payments API | Migration gateway (early access) — transaction search and health probes | https://api.migopayments.com |
At-a-glance comparison
| API | Audience | Auth method | Base URL | Live spec |
|---|---|---|---|---|
| Wallet Gateway | End-user apps, partner backends | JWT (Ed25519) — Authorization: Bearer <token>; applicationId header on config/integrity endpoints | https://api.ali.app/rest | Open Scalar → |
| Middleware | Server-to-server (merchant backends, processors) | JWT — Authorization: Bearer <middleware-jwt> | https://mw.migopayments.com | Open Scalar → |
| CMS Backoffice | Authorized internal/partner operators only | JWT (Ed25519) + user session — Authorization: Bearer <token> + x-user-token | https://api.ali.app/cms/rest | Open Scalar → |
| Migo Payments API | Migration gateway (early access) | JWT — Authorization: Bearer <token> | https://api.migopayments.com | Open Scalar → |
Detailed dimensions
| Dimension | Wallet Gateway | Middleware | CMS Backoffice |
|---|---|---|---|
| Audience | End-user apps, partner backends | Server-to-server | Authorized operators only |
| Auth headers | Authorization (application identity is carried inside the JWT); applicationId header only on config/integrity endpoints | Authorization | Authorization + x-user-token |
| Public access | Open to any Migo customer | Open to any Migo customer | Restricted |
| Domains (illustrative, not exhaustive) | Auth, Users, Cards, Card Transfers, Settlements, Terminal Payments, Leads, Businesses, Reports, Webhooks | Verifications, Suspensions, Subscriptions, Plans, Transactions, Payments, Cards, Auth, Config, Alternative Payments, Webhooks | Authentication, CMS Users, Partners, Cardholders, Process Requests, Permissions, Modules |
Test in the browser
Each reference renders as a live console — pick an endpoint, fill in the required parameters, and send a request. Login once in the "Authentication" block to get a token, then every other endpoint auto-fills the Authorization header.
All references default to production (the first server in each spec). Switch to QA/Sandbox in the server selector dropdown before sending test requests.
OpenAPI specs
The raw OpenAPI 3.0 JSON is public and downloadable:
/openapi/ali-api-gw-rest.json/openapi/migo-api.json/openapi/ali-api-cms-rest.json/openapi/migo-api-gw-rest.json
Use them to generate typed clients with openapi-typescript, oapi-codegen, or any other OpenAPI code generator.
Postman
Import any of the OpenAPI specs above into Postman — it auto-generates a collection.
Next steps
- New to Migo? Start at the Quick Start.
- Looking for concepts? See the Glossary.