Modify

The modify action updates a resting (OPEN status) order without requiring you to cancel and replace it. You can change the price, total size, time-in-force (Gtc or Alo only), and client order ID. Direction (b), contract (a), and reduceOnly (r) cannot be changed — cancel the order and place a new one if you need to alter those fields.

Endpoint

POST https://upsidemax.xyz/exchange
Content-Type: application/json

Priority Rules

How you locate and modify the order determines whether it retains its queue position:

Same price, reduce size only — the modification is applied in-place. The order keeps its existing FIFO queue priority and its order ID.
Change price, increase size, or change TIF/cloid — the order is removed and re-queued at the back of the new price level, losing its queue priority. The order ID is still preserved.

An increase in size passes an initial-margin pre-check before it is re-queued. If margin is insufficient, the order is rolled back to its original parameters and the rejection is reported in statuses[0].error (insufficient margin for modified order).

If the new price would immediately cross the book and match against a resting opposite-side order, the modification request is rejected. Cancel the order and place a new one to execute at a marketable price.

Request

Locate by Order ID
Locate by Client Order ID

Use oid to identify the order by the exchange-assigned ID returned in resting.oid.

{
  "action": {
    "type": "modify",
    "a": 1,
    "oid": 12345,
    "p": "150",
    "s": "8",
    "tif": "Gtc"
  },
  "signature": { "r": "0x...", "s": "0x...", "v": 28 },
  "nonce": 1778858100000,
  "sync": true
}

Use cloid to find the order by its client-assigned ID, and optionally update the client order ID at the same time with c.

{
  "action": {
    "type": "modify",
    "a": 1,
    "cloid": "1778763737044",
    "p": "151",
    "c": "1778858200000"
  },
  "signature": { "r": "0x...", "s": "0x...", "v": 28 },
  "nonce": 1778858200100,
  "sync": true
}

Action Fields

string

required

type (required) — Fixed value: "modify".

int32

required

a (asset) (required) — The integer contract ID of the order to modify.

int64

oid (orderId) — Exchange-assigned order ID from resting.oid. Takes priority over cloid when both are provided. At least one of oid or cloid must be present.

string

cloid — clientOrderId (locate) — Client order ID used to find the order when oid is not provided. Must match the c field set at placement. Only decimal digits (0–9) are accepted, at most 20 bytes, within the int64 range; otherwise the request returns 400 INVALID_PARAM with errors[].reason INVALID_FORMAT (OUT_OF_RANGE outside int64).

string

p (price) — New limit price as a raw integer string. Omit to keep the existing price unchanged.

string

s (size) — New total target size as a raw integer string. This is the total quantity including any already-filled amount, not just the remaining leaves size: the new remaining quantity is s minus the filled amount, so s must exceed what has already filled. Omit to keep the existing size unchanged.

string

tif (timeInForce) — New time-in-force for the order. Only "Gtc" (good-til-cancel) or "Alo" (add-liquidity-only / post-only) are accepted. Omit to keep the existing TIF unchanged.

string

c — clientOrderId (update) — New client order ID to assign to the order after modification. Same format rules as cloid. Omit to keep the existing client order ID unchanged.

boolean

sync — Envelope-level, beside action, and not signed. true returns HTTP 200 with a one-entry statuses[]; false returns HTTP 202 and the results arrive on orderUpdates. When omitted, the server default applies. Must be a JSON boolean. See Synchronous and asynchronous responses.

You must provide at least one of oid or cloid to identify the order. All other fields (p, s, tif, c) are optional — include only the fields you want to change.

Response

The synchronous result has a single shape: response.data.statuses[] with exactly one entry for the modified order, using the same entry grammar as order — resting, filled, or error. No other result shape is returned; read statuses[0].

Two status codes are possible. With sync: true the server answers HTTP 200 with the result shown below; with sync: false it answers HTTP 202, acknowledging the request for asynchronous processing:

{"status": "accepted", "response": {"type": "accepted", "data": {"count": 1}}}

count is always 1. On a 202 the outcome arrives on the orderUpdates channel instead. Without sync the server default decides — handle both.

Resting
Rejected

The order was modified and is resting in the book under its original order ID.

{
  "status": "ok",
  "requestId": "req-144115188075856200",
  "response": {
    "type": "modify",
    "data": { "statuses": [{ "resting": { "oid": 12345 } }] }
  }
}

The modification was rejected and the original order is unchanged. The top-level status is still "ok".

{
  "status": "ok",
  "requestId": "req-144115188075856201",
  "response": {
    "type": "modify",
    "data": { "statuses": [{ "error": "orderId not found" }] }
  }
}

Response fields

array

Exactly one entry, for the modified order. The entry is one of:

resting — { "oid": <int64> }, the modified order is in the book. The order ID does not change.
filled — { "oid": <int64>, "totalSz": "<string>", "avgPx": "<string>" }.
error — a string explaining the rejection. The original order is unchanged.

The response does not carry the modified order’s full state. Read the new price, total size, remaining size, and client order ID from userOrders, or from the orderUpdates channel.

Errors

Modify rejections

These appear as statuses[0].error. The original order is unchanged in every case.

Error	Cause
`orderId not found`	The `oid` or `cloid` does not match any active order
`clOrdId not found`	Located by `cloid`, but no matching active order was found
`order already canceled`	The target order was already cancelled before this request arrived
`order not open`	The order is in a terminal state (fully filled or cancelled)
`new size must exceed already-filled amount`	The requested `s` is less than or equal to the quantity already filled
`modify supports resting TIF only (GTC / POST_ONLY)`	`tif` was set to `"Ioc"` or another non-resting value
`modified price is marketable (would cross the book); cancel and place a new order instead`	The new `p` would immediately match against a resting opposite-side order
`newClientOrderId already in use by an active order`	The `c` value collides with another active order’s client order ID
`insufficient margin for modified order`	Increasing `s` would require more margin than is available; the change is automatically rolled back
`nonce already used`	The signing address already used this `nonce`. Signature and `nonce` rejections are reported in `statuses[0].error` as well.

HTTP errors

HTTP	`code`	Cause
400	`INVALID_PARAM`	A field failed validation; `errors[]` names the field, the `reason`, and the `expected` value. Nothing is submitted.
400	`BAD_REQUEST`	Malformed body, `sync` not a JSON boolean, or the signer has no registered account.
400	`DUPLICATE_NONCE`	A request with the same `nonce` from this signer is still in flight.
401	`SIGNATURE_INVALID`	Signature recovery failed or did not match.
429	`RATE_LIMITED`	Too many requests.
503	`DOWNSTREAM_UNAVAILABLE` / `WARMING_UP`	Temporarily unavailable; retry later, or use `sync: false` when busy.
504	`DOWNSTREAM_TIMEOUT`	No result within the waiting window. The modification may already be applied — reconcile before retrying; see Timeouts and retries.

Overview

Account

Orders

Margin & Leverage

Conditional Orders

Collateral Transfers

API Wallet

Endpoint

Priority Rules

Request

Action Fields

Response

Response fields

Errors

Modify rejections

HTTP errors

​Endpoint

​Priority Rules

​Request

​Action Fields

​Response

​Response fields

​Errors

​Modify rejections

​HTTP errors

Endpoint

Priority Rules

Request

Action Fields

Response

Response fields

Errors

Modify rejections

HTTP errors