Limit & stop orders
02 / 04

Orders that wait for a price

Limit and stop orders live server-side and execute when the market crosses your trigger — no babysitting, and no signature per fill.

The four types

  • limit_buy
    Triggers when
    Price drops to or below your limit
    Use
    Buy a dip without watching the chart
  • limit_sell
    Triggers when
    Price rises to or above your limit
    Use
    Take profit at a target
  • stop_buy
    Triggers when
    Price rises to or above your stop
    Use
    Enter on a breakout
  • stop_sell
    Triggers when
    Price drops to or below your stop
    Use
    Cut a position on a breakdown

Creating one

vectr agent "set a limit buy on 0x… at 20% below the current price, 0.05 ETH"

Or directly — the orders API is session-authenticated:

POST /orders
Create — body: tokenAddress, curveAddress, tokenSymbol, tokenName, type, side, plus the type's params
GET /orders
Your wallet's open orders
PATCH /orders/:id
Reprice — updates the limit price
DELETE /orders/:id
Cancel
GET /orders/history?tokenAddress=
Fills for a token

Parameters and bounds

  • limitPrice
    Bound
    positive
    Notes
    The trigger, in the token's quote asset
  • slippage
    Bound
    0–50%
    Notes
    Tolerance around the trigger at execution
  • expiresAt
    Bound
    ISO date
    Notes
    Optional — dead orders don't sit forever
  • quote amount
    Bound
    positive
    Notes
    How much to spend on buys (the API field predates the rename — it's the pairing-asset amount)
  • tokenAmount
    Bound
    positive
    Notes
    How much to sell on sells

Orders execute from your own custodial wallet when the trigger hits — there is no separate oracle signing your fills. Creating the order is the consent; execution is the consequence.

A trigger is not a guaranteed fill

Price can gap through a limit on a thin curve — the order fires at the trigger, the trade executes at whatever the curve gives within your slippage bound. Size accordingly.