The Olympus public API covers payments, payment links and QR codes, payouts and settlements. You can build against all of it before any real money is involved.
Two kinds of key
- Sandbox keys start with olp_test_. They skip the account-verification requirement, and every call works the same way as a live call.
- Live keys start with olp_live_. Money-moving endpoints need verification to be complete first, the same rule the dashboard itself follows.
Sandbox and live data, including payments, links, QR codes, split recipients and settlements, are always kept completely separate.
Choose the outcome yourself
When a sandbox call returns a checkout URL, it opens a confirmation page where you choose the outcome instead of a real checkout page. The matching webhook event is sent too, so you can test how your server reacts to a success, a failure or a cancellation.
What is the same as production
- Requests are authenticated with Authorization: Bearer <api-key>, and each key is scoped to the endpoints it may call.
- Write requests accept an Idempotency-Key, so a retry returns the original result.
- Webhooks are signed with HMAC-SHA256, so you can verify that an event came from Olympus.
Where to start
Create a sandbox key in the merchant dashboard, read the documentation, or load the OpenAPI spec into your client generator. Every status value and webhook event type is listed in the API reference.