- Docs
- Api%2Freference%2Febus
Actions & fees
Actions are how anything happens: minting a ticket, transferring it, redeeming it, updating what it says. Every action is signed by the wallet behind it, so a change can always be traced back to whoever authorised it — and no party, including Dual, can quietly rewrite history. Running an action takes four steps: 1. `GET /ebus/nonce` — ask for the wallet's next action number. 2. `POST /ebus/prepare` — get back the exact text to sign. You can build this yourself, but asking for it removes any doubt that it matches. 3. Sign it with the wallet — its passkey, or the crypto wallet behind it. 4. `POST /ebus/execute` — send the action and its signature. It is checked, priced and applied in one go. The action number is what stops a signed request being replayed later: once it has moved on, an old copy is worthless. An action that is turned away costs nothing. One that goes through appears in `GET /ebus/action-logs` straight away, and reaches every webhook watching for it. **What it costs.** Each action is paid for from the organization's balance in DUAL. The price has a fixed part and a part that moves with what it actually costs the network to prove the work. Ask `GET /public/network/fees` for today's price before you commit to anything.
https://api.dual.networkBearer JWTx-api-key