API Reference
Migo Payments exposes four REST APIs. Each one has its own interactive reference, rendered with Scalar on a separate page reachable from the table below.
Which API do I need?
| API | What you use it for | Audience | Base URL | Authentication | Reference |
|---|---|---|---|---|---|
| Wallet Gateway | Build a wallet or card program — issue cards, tokenize, charge, transfer, onboard merchants | End-user apps, partner backends | https://api.ali.app/rest | JWT (Ed25519) — Authorization: Bearer <token>. Application identity is carried inside the JWT; the applicationId header is used only on config/integrity endpoints | Open Scalar |
| Middleware (legacy) | Issue hosted Payment Links, run subscription billing, accept alternative payments, manage fraud suspensions | Server-to-server (merchant backends, processors) | https://mw.migopayments.com | JWT — Authorization: Bearer <middleware-jwt> | Open Scalar |
| Migo Payments Gateway (migration, early access) | Transaction search and health probes during the Migo→ALI transition | Integrators explicitly onboarded by Migo | https://api.migopayments.com | JWT — Authorization: Bearer <token> | Open Scalar |
| Credits API v2 | Build your own credit solution — bank affiliation, accounts and transaction lifecycle (Credit Core) | Merchants, fintechs and platforms offering credit to their users | https://api.migopayments.com/v2/credits | Authorization: <token> issued by Migo, validated by a TOKEN Authorizer — see Authentication | Open Scalar |
The Wallet Gateway and the Middleware are open to any Migo customer. The domains each one covers (illustrative, not exhaustive):
- Wallet Gateway — Auth, Users, Cards, Card Transfers, Settlements, Terminal Payments, Leads, Businesses, Reports, Webhooks.
- Middleware — Verifications, Suspensions, Subscriptions, Plans, Transactions, Payments, Cards, Auth, Config, Alternative Payments, Webhooks.
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/migo-api-gw-rest.json/openapi/migo-credits.json
Use them to generate typed clients with openapi-typescript, oapi-codegen, or any other OpenAPI code generator. Importing any of these specs into Postman generates a collection.
Next steps
- New to Migo? Start with the Sandbox Quickstart.
- Looking for concepts? See the Payments Glossary.