DelegatedOrderService enables partners with the delegated_signing scope to place and cancel orders on behalf of sub-accounts. The server signs orders using the sub-account’s managed wallet, so the partner does not handle private keys directly.
Recommended setup: Store your HMAC credentials (
token_id / secret) on your backend. Use this SDK server-side to sign partner-authenticated requests. Expose only your own app-specific endpoints to the frontend. Never expose HMAC secrets in browser bundles or client-side storage.Access
Create a GTC delegated order
post_only: true when the order must rest on the book:
Create a FAK delegated order
FAK orders useprice and size, then cancel any unmatched remainder:
Create a FOK delegated order
FOK orders execute immediately or cancel entirely. They usemaker_amount:
Parameters
CreateDelegatedOrderParams
Cancel an order
Cancel all orders in a market
How it works
- The SDK builds an unsigned order locally with a zero verifying address.
- It sends
owner_idandon_behalf_ofas the sub-account profile ID. - The backend detects delegated-signing scope and signs the order with the managed wallet.
- The signed order is submitted to the exchange engine.