Skip to main content
Some explicitly on-chain Aura operations still return an unsigned Alephium transaction under /v1/tx/*. Trading does not: instant orders are signed and submitted internally under the user’s restricted enclave authorization.
The former /v1/tx/markets/{address}/orders, market-orders, and order-cancel builders are deleted. An integration that still calls them is using the legacy on-chain CLOB model and must migrate before launch.

​
Where build-tx still applies

Always use the current OpenAPI operation for the exact request and response. Wallet collateral deposits and withdrawals use the session-bound /v1/funding flow, not a generic build-tx tutorial.

​
Safe flow

1

Read protocol configuration

Confirm network, contract addresses and collateral token from GET /v1/protocol/config.
2

Build for the authenticated signer

The route verifies that the requested signer matches the wallet session. Validate the returned network, destination, token movements and expiry in your own client before asking for a signature.
3

Sign without exporting custody material

Send the unsigned transaction to the user’s wallet provider. Never request or export a raw seed, and never send a private key to Aura or to your backend.
4

Submit to Alephium

Submit the signed transaction through a trusted node/provider. Do not reuse a signature for a different unsigned payload.
5

Reconcile generically

Poll GET /v1/transactions/{txId} or use the corresponding realtime topic. The generic response distinguishes mempool, confirmation, script failure, local indexing, reorg and recovery state.

​
Validate before signing

At minimum compare:
  • the chain/network and contract against /v1/protocol/config;
  • the authenticated signer address;
  • token IDs and exact base-unit amounts;
  • the operation-specific bounds and expiry;
  • the expected contract method and destinations;
  • any fee and refundable-deposit assumptions.
Treat the unsigned transaction as untrusted input until this comparison passes.

​
Retry semantics

Building is generally side-effect free, but the surrounding operation may have an idempotency contract. Follow the endpoint’s documented idempotency key and do not assume every POST is safe to duplicate. Once a transaction has been submitted, reconcile its transaction ID rather than blindly building and submitting a replacement.

Prepare API trading

Use the instant clearinghouse authorization model for orders.

Native funding

Read spendability and use the exact-vector withdrawal flow.

API errors

Handle node, validation and reconciliation failures.
Last modified on August 11, 2026