Close a position

Get out of a position the way the trader means to: take some off, get flat on one instrument, get flat on everything, or turn the position around. Use this page to choose the right call for each button on your screen. The four calls differ in one thing, which is what they cancel before they trade. By the end you know which to use when, and what each one leaves behind.

Call	Cancels first	Then	Leaves
Close part of a position	Nothing	Sells or buys `qty` at market	The rest of the position and every working order
Flatten a position	That instrument’s working orders	Closes its position at market	Every other instrument as it was
Flatten the account	Every working order on the account	Closes every position	Nothing
Reverse a position	That instrument’s working orders	Trades twice the position at market	A position the same size, the other way

Before you start

The examples use the variables from the programmatic quickstart and a long position of 2 ESZ6, the December 2026 E-mini S&P 500 contract, on a Demo in production. A Demo prices futures only from your own futures login, as Place your first order explains, so in the sandbox you run the same calls on a HYPERLIQUID:BTC position, sized in bitcoin, as Test it end to end does. The TypeScript SDK isn’t published, so call the routes over HTTP, as the curl examples do. The TypeScript examples show the same calls through the SDK’s client, with provider and account set.

On a Demo, a futures close fills only while the CME session is open. Outside it, a flatten still cancels the working orders, but the position stays and the call answers contract_not_trading.

Take some off

Close part of a position trades qty against the position at market and cancels nothing, so the bracket keeps protecting what’s left.

curl -X POST "$TRDRS_API_BASE_URL/api/trading/close?provider=$PROVIDER&account=$ACCOUNT" \
  -H "Authorization: Bearer $TRDRS_TRADING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "instrument": "ESZ6",
    "qty": 1,
    "clientOrderId": "close-esz6-1"
  }'

await client.trading.closePartOfAPosition({
  provider,
  account,
  instrument: 'ESZ6',
  qty: 1,
  clientOrderId: 'close-esz6-1',
})

The response names the close order with providerOrderId, filledQty and avgFillPrice, and requestedQty repeats the quantity you asked to close. The position is now 1 contract. A close is an order, so it carries a clientOrderId like any other, and a retry with the same id can’t close twice.qty can’t be more than the position. A close that’s too big is refused rather than cut down to fit, because the position may have changed since you read it, and “close 3” must never quietly become “close everything”. To close it all, flatten.On an account that holds each entry as its own ticket, send the ticket’s positionId to close that ticket alone. Add positionRevision, the revision you read the ticket at, and the close is refused if the ticket has changed since.

Get flat on one instrument

Flatten a position cancels the instrument’s working orders first, then closes the position at market. That order matters: a resting order left behind could open the position again after the close.

curl -X POST "$TRDRS_API_BASE_URL/api/trading/flatten?provider=$PROVIDER&account=$ACCOUNT" \
  -H "Authorization: Bearer $TRDRS_TRADING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "instrument": "ESZ6" }'

await client.trading.flattenAPosition({ provider, account, instrument: 'ESZ6' })

The response is { "ok": true }. Flattening a flat instrument changes nothing, so it’s safe to repeat, and it’s the right last step of every test run.

Get flat on everything

Flatten the account cancels every working order and closes every position on the one account you name. It never touches your other accounts.

curl -X POST "$TRDRS_API_BASE_URL/api/trading/flatten-account?provider=$PROVIDER&account=$ACCOUNT" \
  -H "Authorization: Bearer $TRDRS_TRADING_API_KEY"

await client.trading.flattenTheAccount({ provider, account })

The response is { "ok": true }.

Flattening the account can’t be undone. Ask the trader to confirm before you call it.

Turn the position around

Reverse a position cancels the instrument’s working orders, then trades twice the position at market, so a long of 2 becomes a short of 2. It runs on the server as one operation under one clientOrderId. Doing it yourself as a cancel followed by an order could stop half way and leave the trader flat, or turned around without protection.

curl -X POST "$TRDRS_API_BASE_URL/api/trading/reverse?provider=$PROVIDER&account=$ACCOUNT" \
  -H "Authorization: Bearer $TRDRS_TRADING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "instrument": "ESZ6",
    "clientOrderId": "reverse-esz6-1"
  }'

const reversed = await client.trading.reverseAPosition({
  provider,
  account,
  instrument: 'ESZ6',
  clientOrderId: 'reverse-esz6-1',
})

For a long of 2, the response says what traded and how many orders it cancelled:

{
  "providerOrderId": "reverse-esz6-1",
  "filledQty": 4,
  "avgFillPrice": 6478.75,
  "cancelledOrders": 2,
  "side": "sell",
  "qty": 4
}

The new position has no bracket, because the old one protected the other direction. Put a new one on it with Protect a position.

Which one to use

Scaling out of a winner: close part. The bracket keeps protecting the rest.
Done with the trade: flatten the instrument. It clears the resting orders first, so nothing puts the trader back in.
Done for the day, or something is wrong: flatten the account.
On the wrong side of the market: reverse. Doing it by hand takes three calls, and each is a chance to stop half way.

To clear resting orders without touching the position, use Cancel all working orders instead of a flatten.

When a close is refused

Call	Status	Code	What it means	What to do
Close part	`400`	`close_exceeds_position`	`qty` is more than the position.	Flatten to close it all, or send a smaller `qty`.
Close part	`400`	none	There’s no position on the instrument.	Read the account.
Close part	`400`	`position_close_unsupported`	You sent a `positionId` to an account whose provider doesn’t name positions.	Close by instrument.
Close part	`409`	none	This `clientOrderId` was already used. The first close stands.	Read the account.
Close part	`409`	`risk_locked`	A hold is on the account and the provider can’t guarantee the close only reduces.	Flatten the instrument instead.
Close part	`409`	`position_revision_stale`	The ticket changed after the `positionRevision` you sent.	Read the account, then decide again.
Close part	`422`	`position_not_closable`	The ticket you named isn’t open on the instrument, is held on the side the close trades, or holds less than `qty`.	Read the account.
Close part, reverse	`422`	`market_data_unavailable`	On a Demo, no price can reach the instrument. With `params.cause` `login_missing`, you’ve connected no login that carries futures prices.	Retry with the same id once a price arrives, or connect such a login in production.
Reverse	`400`	none	There’s no position to reverse.	Read the account.
Reverse	`403`	`feature_disabled`	Live trading is switched off for you, and a reverse opens new exposure at a provider. Your Demo isn’t affected.	Contact trdrs.
Reverse	`409`	none	This `clientOrderId` was already used. The first reverse stands.	Read the account.
Reverse	`409`	`position_changed`	The position changed while its orders were being cancelled, so the reverse stopped before trading. `cancelledOrders` says how many went.	Read the account, then decide again.
Reverse	`423`	`risk_locked` or `reconciliation_hold`	A hold is on the account. Reversing opens new exposure, so it’s refused.	Show the hold.
Flatten the account	`400`	none	No account is connected.	Connect an account.

Neither flatten checks the risk lock, because getting flat is what a lock asks for.

Test it end to end

On your Demo in the sandbox, with HYPERLIQUID:BTC sized in bitcoin:

Buy 0.02 with a take profit and a stop loss, then close 0.01. The position is long 0.01.
Reverse. The position is short 0.01, and cancelledOrders counts the bracket’s orders it took down.
Flatten the account, then read the snapshot: no positions and no working orders.

Start here

Trading

Before you start

Which one to use

When a close is refused

Test it end to end

Next steps

Track fills and P&L

Manage working orders

​Before you start

​Which one to use

​When a close is refused

​Test it end to end

​Next steps

Track fills and P&L

Manage working orders

Before you start

Which one to use

When a close is refused

Test it end to end

Next steps