TheDocumentation Index
Fetch the complete documentation index at: https://limitless-docs-ws-settlement-events.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
DelegatedOrderService enables partners with the delegated_signing scope to place and cancel orders on behalf of their sub-accounts. The server signs orders using the sub-account’s managed Privy wallet — no private key management is needed on the partner side.
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
Builds an unsigned GTC (Good-Til-Cancelled) limit order and submits it toPOST /orders with the on_behalf_of profile ID. The server signs the order via the sub-account’s managed wallet. GTC orders remain on the orderbook until filled or explicitly cancelled.
post_only=True to ensure the order only rests on the book and is never filled immediately as a taker:
Create a FAK delegated order
FAK (Fill-And-Kill) orders use the sameprice and size inputs as GTC, but they only consume immediately available liquidity and cancel any unmatched remainder.
post_only is not supported for FAK orders.
Create a FOK delegated order
FOK (Fill-Or-Kill) orders execute immediately at the best available price or are cancelled entirely — there are no partial fills. Instead ofprice and size, FOK orders use maker_amount:
- BUY:
maker_amountis the USDC amount to spend (e.g.,50.0= spend $50 USDC) - SELL:
maker_amountis the number of shares to sell (e.g.,18.64= sell 18.64 shares)
Parameters
GTC order parameters
| Parameter | Type | Description |
|---|---|---|
token_id | str | Position token ID (YES or NO) from market data |
side | Side | Side.BUY or Side.SELL |
order_type | OrderType | OrderType.GTC |
market_slug | str | Market identifier |
on_behalf_of | int | Profile ID of the sub-account |
price | float | Price between 0 and 1 |
size | float | Number of contracts |
post_only | bool | Optional. True rejects the order if it would immediately match. Default False. |
fee_rate_bps | int | Fee rate in basis points (defaults to 300 if omitted) |
FAK order parameters
| Parameter | Type | Description |
|---|---|---|
token_id | str | Position token ID (YES or NO) from market data |
side | Side | Side.BUY or Side.SELL |
order_type | OrderType | OrderType.FAK |
market_slug | str | Market identifier |
on_behalf_of | int | Profile ID of the sub-account |
price | float | Price between 0 and 1 |
size | float | Number of contracts |
fee_rate_bps | int | Fee rate in basis points (defaults to 300 if omitted) |
FOK order parameters
| Parameter | Type | Description |
|---|---|---|
token_id | str | Position token ID (YES or NO) from market data |
side | Side | Side.BUY or Side.SELL |
order_type | OrderType | OrderType.FOK |
market_slug | str | Market identifier |
on_behalf_of | int | Profile ID of the sub-account |
maker_amount | float | BUY: USDC to spend. SELL: shares to sell. Max 6 decimals. |
fee_rate_bps | int | Fee rate in basis points (defaults to 300 if omitted) |
Cancel an order
Cancel on behalf of a sub-account
Cancel all orders in a market
Cancel all on behalf of a sub-account
How it works
- The SDK builds an unsigned order locally with a zero verifying address
- For GTC and FAK orders,
priceandsizeare used; for FOK orders,maker_amountis used (withtaker_amountalways set to 1) - The order is posted to
POST /orderswithon_behalf_ofandowner_idset to the sub-account’s profile ID - The server detects the
delegated_signingscope and missing signature - The server looks up the sub-account’s server wallet, builds EIP-712 typed data, and signs via Privy
- The signed order is submitted to the CLOB engine — GTC orders can rest on the book, FAK orders cancel unmatched remainder, and FOK orders either fully fill or cancel