Sandbox fair-use rules
The limits that apply to every Mesta sandbox, version sandbox-2026-10: API requests, sandboxes and users, simulated activity, orders and uploaded documents, and what happens when a sandbox reaches a limit.
Sandbox fair-use rules
Version sandbox-2026-10. These rules set the limits referred to in the Sandbox Terms. They apply equally to traffic from people, scripts and AI agents.
| Limit | Value |
|---|---|
| API requests per sandbox, all its keys and portal sessions together | 300 per minute and 20,000 per day until you verify your email address, then 600 per minute and 100,000 per day |
| Sandboxes per person | 1 live sandbox for each email address and account |
| Approved users per sandbox | 1. Colleagues cannot be added |
| Simulated deposits per sandbox per day | 50, for 500,000 currency units in total |
| Other simulated status changes and re-sent events per sandbox per day | 200 |
| Orders per sandbox | 1,000 at a time. A reset deletes the orders and frees the room |
| Documents uploaded for senders and beneficiaries | In the onboarding wizards, Mesta's specimen files only. 5 MiB per document and 50 MiB per sandbox. Deleted with the sandbox, and in any case 90 days after upload |
| Senders, beneficiaries and source wallet addresses | 1,000 of each per sandbox |
| Objects per request | At most 50, for example source wallet addresses added in one request |
| Order documents | 5 per order and 1,000 per sandbox. Deleted with the sandbox. They do not count toward the 50 MiB for sender and beneficiary documents |
| API keys | 5 per sandbox. A rotated key's predecessor keeps working for 24 hours and is not counted |
| Webhook endpoints | 3 per sandbox, HTTPS only, at a public address |
| Resets | 50 per sandbox per day |
| Requests per network address | Counted before the API, per 5 minutes: 2,000 to the API, and 100 to the sign-in routes, of which 25 sign-ins and second-factor steps and 60 token refreshes, and 10 to the password-reset routes |
| Portal sign-in | 10 failed attempts per account and 50 attempts per network address, per 15 minutes. The per-address limits in the row above also apply, and whichever is reached first refuses the attempt |
| Email verification codes | 3 per email address per hour and 10 per day |
| Requests for production access | 1 per sandbox per day |
A day is the 24 hours before each request.
When a limit is reached, the API refuses the request. A limit on requests or attempts, including sign-in, email codes and requests for production access, answers HTTP status 429 and says when to try again. A limit on what one sandbox holds or does answers 409 with the error code SANDBOX_CAP_EXCEEDED. Repeated or deliberate attempts to exceed or get around a limit may lead to suspension under section 16 of the Sandbox Terms.
Whatever the limits, the sandbox may not carry production or commercial traffic or be load-tested. You may also not resell or share access outside your organization, impersonate a person or a business, represent sandbox output as real funds or transactions to anyone, or attempt to reach production with sandbox credentials or data (section 13 of the Sandbox Terms).
To ask for a higher limit, write to [email protected] with your sandbox id. Mesta may change these limits, with notice in the sandbox documentation.
Updated 1 day ago

