Skip to main content
Most endpoints need your API key. A few are public and need nothing:
  • API key needed: creating checkout sessions, and every off-ramp and onramp endpoint.
  • Nothing needed: checking a session’s status, looking up payment link info, and starting a payment from a payment link.
The Wallet API is a separate product with its own wsk_live_ keys, which you create under Dashboard → Wallets instead of API Keys. See its own pages for details. The rest of this page is about the ms_live_ key used everywhere else.

​
API key

Every key starts with ms_live_.
Keep your API key on your server. Never put it in website code, a mobile app, or a public code repository, where anyone could copy it.

​
Example

​
Create a key

  1. Open merchant.minisend.xyz/dashboard.
  2. Go to API Keys and click New Key.
  3. Copy the key straight away. We only show it once, and we don’t keep a readable copy, so we can’t show it to you again.
A 401 means the key is missing or wrong. A 403 means your account can’t use that product yet. See below.

​
Key scopes

What your key can do depends on which products are switched on for your account. Turning a product on works for every key you have, including new ones. Until a product is on, calls to it get a 403 like this:

​
Rate limits

You can make up to 60 requests a minute from one IP address. Each response has an X-RateLimit-Remaining header showing how many you have left. Go over, and you get a 429. Endpoints that move money or send a real payment prompt have their own, tighter limits. These count per account, not per IP address: The onramp also sends at most 5 payment prompts to the same phone number in 10 minutes, whoever is asking. A 429 here means that phone got a prompt very recently, not that your whole account is slowed down. Need higher limits? Get in touch with support.

​
Public endpoints

These need no Authorization header: They’re safe to call from a browser or mobile app.