Authentication
Every request carries your API key as a bearer token:
Authorization: Bearer vmk_live_…
A missing, unknown or revoked key gets 401 UNAUTHENTICATED.
Creating and revoking keys
Owners and developers manage keys under Developers → API keys in the dashboard. Each create or revoke is confirmed with a code emailed to you.
Keeping keys safe
- A key is shown once, when it is created. Vmonie keeps only a fingerprint of it and cannot show it again. If a key is lost, create a new one and revoke the old one.
- Use the key from your servers only. Never put it in a mobile app, a browser or a public repository: anyone holding it can spend your wallet.
- You can hold more than one key, for example to rotate: create a new key, deploy it, then revoke the old one. A revoked key stops working at once.
IP allowlist
Restrict your API keys to your servers' IP addresses or ranges (for
example 203.0.113.10 or 203.0.113.0/24) under Developers → IP
allowlist in the dashboard. Requests from anywhere else get
403 IP_NOT_ALLOWED, even with a valid key. An empty list allows any
address. We recommend setting it for every production account. Add your
new servers before moving traffic to them.
Account status
If your business account is suspended, every request gets
403 BUSINESS_NOT_ACTIVE. Your wallet balance is kept. Contact Vmonie.
Rate limits
Each key may make up to 120 requests a minute. Above that you get
429 TOO_MANY_REQUESTS; wait a little and retry. Cache the biller and
product lists rather than fetching them before every payment.