Recipes
SET API and SET Direct Deposit API · 2026-11-10
A recipe is a complete integration in order, from the first call to the event that says it worked. Each one has a guide in SET Docs and a folder in its Postman collection. On staging, each recipe runs from start to finish with a self-serve sandbox key. Each step that needs money, a payee or a signature runs its simulator instead.
| Recipe | API | What it does | On staging, simulated |
|---|---|---|---|
| Exact-net payout | SET Direct Deposit API | Pays a payee's bank an exact amount, once per reference: quote, check, reserve, send, set the reference, payout_intent.paid | The payee's Cash-Out Address, the payout and its bank leg |
| Pay from a Payout Safe | SET Direct Deposit API | Registers a Safe your people sign for, resolves a batch, exports it for Safe Transaction Builder, and reports the multisend | The Safe (an ordinary wallet signs instead) and the multisend |
| Wallet everywhere, bank in the US | SET Direct Deposit API | Pays anyone by email into their own wallet at once. One event means paid: payable_payment.in_wallet | The payment into the payee's wallet |
| Marketplace split | SET API | Collects one buyer payment into the seller's wallet, then pays each share in one payout batch | The seller's verification, the buyer's bank transfer, the wallet balance, and each payout's steps |
Running one
- Get a sandbox key for the recipe's API.
- Import its Postman collection, and set the key and the recipe's input variables.
- Run the recipe's folder in order. Keep 12 seconds between requests: a self-serve key allows only a few writes a minute.
Each guide explains every step and what it is for. Each guide also says which steps are yours in production.