Place a new limit order
Place a conditional order that triggers automatically when a price threshold is crossed. Supports two target types: "token" (default) triggers on individual token price, "stack" triggers on the stack NAV (net asset value). Supports limit buys (buy + lte), stop losses (sell + lte), take profits (sell + gte), and breakout buys (buy + gte). Balances are checked at fill time only — no escrow.
Token orders: Require token_address. A company stack is auto-created for the token if needed.
Stack orders: Require stack_id and target_type=stack. Company stacks (single-token) are not allowed — use token orders instead.
Limits: 20 active orders per user, 1 active order per token per user, 1 active stack order per stack per user, minimum buy amount 1 USDC.
ApiKeyAuthX-API-KEY<token>API key with the ix_ prefix. You can generate an API Key by navigating to Settings -> API Key in the web app. Pass it in the X-API-KEY header on every request.
application/json- body
target_type?stringOrder target type. "token" for individual token price, "stack" for stack NAV
"token""token""stack"token_address?stringSolana token mint address (required for token orders)
stack_id?integerStack ID (required for stack orders)
side?stringOrder direction. "buy" purchases the token with USDC, "sell" sells existing holdings
"buy""sell"condition_type?stringPrice comparison. "lte" triggers when price <= target, "gte" triggers when price >= target
"lte""gte"trigger_price?numberUSD price threshold that triggers the order. Must be > 0
amount?numberFor buys: USDC amount (minimum 1 USDC). For sells: percentage of holdings (0-100)
expires_at?|Optional unix timestamp for order expiration. Must be in the future. Omit for no expiry
Order placed successfully.
application/json- response
Subset of limit order fields returned by the place action. Does not include token metadata or display fields.
order_id?string16-character unique order identifier
status?"ACTIVE""ACTIVE"target_type?stringWhether this order targets a single token or a multi-token stack
"token""stack"token_address?|Solana token mint address (present for token orders, absent for stack orders)
side?string"buy""sell"condition_type?string"lte""gte"trigger_price?numberTarget USD price threshold
amount?numberFor buys: USDC amount. For sells: percentage (0-100)
stack_id?integerStack ID — company stack for token orders, user stack for stack orders
stack_name?|Stack name (only present for stack orders)
swap_provider?string"jupiter""dflow"created_at?integerUnix timestamp of order creation
expires_at?|Unix timestamp for automatic expiration, or null if no expiry
curl -X POST 'https://api.indexify.finance/api/limit_orders.php?action=place' \ -H 'Content-Type: application/json' \ -d '{}'{ "order_id": "aBcDeFgHiJkLmNoP", "status": "ACTIVE", "target_type": "token", "token_address": "So11111111111111111111111111111111111111112", "side": "buy", "condition_type": "lte", "trigger_price": 120, "amount": 50, "stack_id": 0, "stack_name": "string", "swap_provider": "jupiter", "created_at": 0, "expires_at": 0}Portfolio, charts, and position visibility POST
Optimized portfolio read, plus the hidden-positions surface. A **position** is one (user, stack) pair — an entry in `stacks`, valued as the sum over its tokens of amount × spot price. A position worth less than $1.00 that could be priced completely AND that the user never bought on the platform is hidden by default (wallets get dusted constantly). A position the user bought here is never hidden automatically, however far it has fallen. A user can hide any position, or pin any position the automatic rule would hide. At this threshold most of a small portfolio can be hidden, so a client MUST surface `hidden_positions` (`count`, `total_value`) wherever it renders the list — an empty list shown without it reads as "your portfolio is gone". Hidden positions (dust and manual) are excluded from `grand_total_stack_value`, `grand_invested_value`, `grand_invested_capital` and the live point of `action=charts`; `pct_of_portfolio` is a share of that shown-only total. `hidden_positions.total_value` reports what was left out. See /docs/api/hidden_positions.md.
Cancel an active limit order POST
Cancel a limit order that has not yet been triggered. Only orders in ACTIVE status can be cancelled. Orders in TRIGGERED, FILLING, FILLED, FAILED, or CANCELLED status cannot be cancelled. The order is removed from both the database and Redis.