Developer Resources · API Basics
API Overview
How the Monime API is designed — REST conventions, Live and Test modes, Space-scoped multi-tenancy, and dated releases.
Monime’s API is your gateway to building modern, flexible, and truly borderless payment experiences. Whether you’re creating a hosted checkout, managing financial accounts, or orchestrating payouts across banks, mobile money, cards, and wallets, the API gives you a single, consistent interface to do it all.
It’s built on REST principles, with predictable resource-oriented URLs, JSON request and response bodies, standard HTTP verbs and status codes, and secure bearer token authentication. Every request is designed for reliability and safety—idempotency keys prevent duplicate operations, cursor-based pagination makes data fetching predictable, and rich metadata helps you tailor resources to your business logic.
Live and Test Modes
You can work in two completely separate environments:
mon_.mon_test_.The access token you use determines the mode. See Environments for details.
Multi-Tenancy by Design
With Monime’s API, every call lives inside a Space—your own secure, self-contained payment world. Each Space has its own accounts, policies, and event streams, completely isolated from others.
Monimeers can work across multiple Spaces, but tokens only unlock what’s allowed by both their scopes and Space permissions. The result is bulletproof isolation, precision access control, and the freedom to power many organisations with a single integration.
Built for Evolving Needs
Monime’s API is designed to evolve at your pace. Each version combines a release name and a date, giving you a clear, predictable view of how the API behaves.
Webhooks are sent using the latest version of the release you’ve selected—giving you dependable stability with the advantage of continuous enhancements.