gdex-limit-orders

You create secure limit orders by calling limitBuy() or limitSell() with your apiKey, userId, sessionPrivateKey, chainId, tokenAddress, and amount. This automates limit-order management using custody-encrypted payloads.

You need authentication via loginWithApiKey() and must meet per-chain minimum order sizes before placing custody-encrypted limit orders. Valid ABI-encoded parameters are also required for safety.

You can list all active limit orders, update prices or amounts, and cancel existing orders across supported chains using dedicated endpoints for buy, sell, and updates.

Yes, the limit order management system supports take-profit and stop-loss semantics. It validates ABI-encoded parameters to safely automate these strategies across supported chains.

Limit orders fail validation when ABI-encoded parameters are invalid or per-chain minimum order sizes are not met. The system enforces these constraints to ensure safe custody-encrypted payload processing.

The best way to manage programmable limit order lifecycles is using a custody-encrypted system that handles creation, listing, updating, and cancellation with dedicated endpoints for buy, sell, and updates.