Aesesdocs

Postman Collection

The official Aeses Postman collection ships every public endpoint pre-organized into folders, with authentication, baseUrl, and idempotency keys already wired up. Import once and you can hit the API without writing a single request from scratch.

Download

Two files: the collection itself (requests grouped by resource) and an environment with the variables they reference.

Download collection

Download environment

What's inside

  • Folders by resource — Deposits, Withdrawals, Balances, Assets, Webhook Deliveries.
  • Collection-level auth — every request inherits x-api-key: {{apiKey}} automatically.
  • baseUrl variable — switch hosts (sandbox vs. production) without touching individual requests.
  • Idempotency-Key pre-filled with {{$guid}} — Postman regenerates a fresh UUID on every send, so retries are safe out of the box.
  • Sample bodies and query strings — every POST and list endpoint ships with a realistic example you can edit and run.

Import in Postman

  1. Open Postman and click Import (top-left).
  2. Drag both downloaded files in, or use Files → Upload.
  3. In the environment selector (top-right), pick Aeses — Production.
  4. Click the eye icon and set apiKey to your secret key (sk_live_… or sk_test_…).
  5. Open any request — for example, Balances → List balances — and hit Send.
Use test keys while you explore

The default environment is named Production but is safe to use with a sk_test_… key — Aeses routes the request based on the key prefix. Switch to a sk_live_… key only when you are ready to move real funds.

Variables

| Variable | Default | Where to set | | ----------- | ------------------------ | --------------------------- | | baseUrl | https://api.aeses.io | Environment — change to point at sandbox if needed. | | apiKey | sk_live_replace_me | Environment — paste your secret key. Stored as a secret-type variable. | | {{$guid}} | auto-generated | Postman dynamic variable — used in Idempotency-Key. Nothing to configure. |

Keeping it up to date

The collection is regenerated from the same descriptor used to validate the public API. Every time the docs site builds, the files served from /aeses.postman_collection.json and /aeses.postman_environment.json are refreshed — re-import to pick up new endpoints.