Skip to main content
A ready-made Postman collection runs the sandbox flows end to end: open an account, receive a simulated deposit, save a counterparty, send a payout, check balances and events, and clean up. Use it to see the API work before you write a line of code, or to check that a sandbox key and its scopes are set up correctly. The collection and its environment file are published at github.com/augustus/postman-collections. They are generated from the published OpenAPI document, so the requests match the current 2026-05-01 API.

​
What it runs

Each folder is independent. Run one at a time.

​
Prerequisites

  • Postman, app or web.
  • A sandbox API key with simulations:write, accounts:read, counterparties:write, payouts:read, payouts:write, deposits:read and events:read. The Webhook folder also needs webhook_subscriptions:write and webhook_deliveries:read. full_access covers all of them. See Scopes.
  • For the Webhook folder, a public HTTPS receiver that answers with a 2xx status. A temporary inbox such as webhook.site is enough.

​
Run it

1

Download the files

Get augustus-v1.postman_collection.json and augustus-sandbox.postman_environment.json from the repository.
2

Import them

In Postman, select Import and add both files. The Augustus Banking API Sandbox Flows collection and the Augustus Sandbox environment appear.
3

Set your key

Select the Augustus Sandbox environment and set apiKey to your sandbox key. Set webhookUrl only if you run the Webhook folder.
4

Run a folder

Open the collection, choose a rail folder, select Run folder and keep the requests in their order.
The collection accepts only https://api.sandbox.augustus.com (or a local loopback address) as base URL, so it cannot run against production. Set cleanupAccount to false to keep the generated account and inspect it in the Dashboard. Cleanup is best-effort: if a run fails before its last steps, the account stays open. Closed accounts and created counterparties remain visible in the sandbox history.
To build the same flow step by step, or to simulate failures, returns and SWIFT specifics, follow Simulations.