Skip to main content
Migo Docs

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?​

APIWhat you use it forAudienceBase URLAuthenticationReference
Wallet GatewayBuild a wallet or card program — issue cards, tokenize, charge, transfer, onboard merchantsEnd-user apps, partner backendshttps://api.ali.app/restJWT (Ed25519) — Authorization: Bearer <token>. Application identity is carried inside the JWT; the applicationId header is used only on config/integrity endpointsOpen Scalar
Middleware (legacy)Issue hosted Payment Links, run subscription billing, accept alternative payments, manage fraud suspensionsServer-to-server (merchant backends, processors)https://mw.migopayments.comJWT — Authorization: Bearer <middleware-jwt>Open Scalar
Migo Payments Gateway (migration, early access)Transaction search and health probes during the Migo→ALI transitionIntegrators explicitly onboarded by Migohttps://api.migopayments.comJWT — Authorization: Bearer <token>Open Scalar
Credits API v2Build your own credit solution — bank affiliation, accounts and transaction lifecycle (Credit Core)Merchants, fintechs and platforms offering credit to their usershttps://api.migopayments.com/v2/creditsAuthorization: <token> issued by Migo, validated by a TOKEN Authorizer — see AuthenticationOpen 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:

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​