Playground
Build a request for any Monato API operation, check it against the OpenAPI spec as you type and send it to a mock sandbox. You get a simulated response, a step-by-step debug path and the webhooks the call would trigger.
Responses are simulated. The mock runs entirely in your browser. Nothing is sent to Monato or anywhere else, and no money moves.
Mock responses are built from the examples and schemas in the OpenAPI specs and a few rules from the guides. Use them to learn the flow and debug your payloads, then test with your real sandbox credentials.
API keys, tokens and secrets last only for this session: they stay in memory and are cleared when you reload or close the page.
Loading the playground…
What the mock checks
- Schema. Required fields, types, enums, patterns, lengths and ranges from the spec. CLABE fields also get the public check-digit test.
- Authentication. The headers each spec asks for. Fincore bearer tokens must come from Create authentication token in this mock, and last 24 hours. Cash requests must carry a valid HMAC-SHA256 signature of
timestamp + "." + body. - Idempotency. Fincore Money Out and Direct Debit charges replay the original response for the same key and body, and reject the same key with a different body. Gift Card purchases reject a repeated
idempotency_key. - State. Ids from earlier steps (client secret, token, instruments, transactions, customers, references) are saved as variables and checked by later steps.
Variables, history, drafts and the mock sandbox state are saved in this browser's local storage under keys that start with mdocs:, without API keys, tokens or secrets. Reset sandbox clears the mock state.