Postman collections
SET API, SET Merchant API and SET Direct Deposit API · 2026-11-10
Two Postman collections (format v2.1) hold every call SET Docs documents, grouped as in this reference. Each one opens with its recipe folders. They are generated from the APIs' own OpenAPI documents, so they match what the APIs accept.
| Collection | Key variable | Download |
|---|---|---|
SET API and SET Merchant API (/v1) | setApiKey: a set_test_… key | set-api.postman_collection.json |
SET Direct Deposit API (/api/partner) | setPartnerKey: a set_partner_… key | set-direct-deposit.postman_collection.json |
Import
- In Postman, choose Import, then Link, and paste the address of a collection above:
https://simpleeasytransactions.com/postman/set-api.postman_collection.jsonhttps://simpleeasytransactions.com/postman/set-direct-deposit.postman_collection.json
You can also download the file and drop it in.
- Open the collection's Variables and set the key variable to your test key (Get a sandbox key).
baseUrlis staging. Leave it there while you use a test key.
Every request sends the key as a bearer token. Every POST sends a fresh Idempotency-Key ({{$guid}}), so running a request again makes a new object. To test a replay, set the header to a fixed value (Idempotency).
Recipe folders
| Folder | Collection | Guide |
|---|---|---|
| Recipe: Exact-net payout | SET Direct Deposit API | Recipe: exact-net payout |
| Recipe: Payout Safe | SET Direct Deposit API | Recipe: pay from a Payout Safe |
| Recipe: Wallet everywhere, bank in the US | SET Direct Deposit API | Wallet everywhere, bank in the US |
| Recipe: Marketplace split | SET API | Marketplace splits |
A recipe's inputs (an email, an amount, your reference) are collection variables. Set them first. Each request's test script checks the status and keeps what the next request needs, such as a payee id, an amount or a transaction hash. Run the folder top to bottom, by hand or with the Collection Runner.
A self-serve sandbox key allows only a few writes a minute. In the Collection Runner, set a delay of 12,000 ms between requests. Otherwise a request answers 429 rate_limited; wait a minute and run it again.
Calls named "(staging) …" are the simulators that stand in for a step outside SET (Simulators). The folder's description lists every step, including the ones outside SET.
In production
Set baseUrl to https://wallet.simpleeasytransactions.com and use a live key. Skip the "(staging)" calls: in production you do those steps yourself, and SET's answers then carry real money and real events. A test key is refused by production, and a live key by staging (Environments and sandbox).
What is not in them
A call appears here once SET Docs documents it. Calls that are switched off, or not yet in this reference, are left out of both the collections and the OpenAPI documents.