For the complete documentation index, see llms.txt. This page is also available as Markdown.

Replace Limit Order

Atomically creates a replacement order and cancels the referenced open order. The replacement receives a new limitOrderId.

Endpoint: POST /api/v1/limit-orders/limit/{limitOrderId}/replace Auth: Required (Authorization: Bearer YOUR_API_KEY)

Headers

Header
Type
Required
Description

Idempotency-Key

string

Yes

Required opaque dedupe token. Use UUIDv4 or ULID. Allowed characters: A-Z, a-z, 0-9, ., _, :, -. Max 200 chars.

Path parameters

Parameter
Type
Required
Description
Example

limitOrderId

string

Yes

Existing open order to replace

lim_abc123

Request body

Request shape matches POST /api/v1/limit-orders/limit.

Field
Type
Required
Description
Example

fromChain

string

Yes

Source chain identifier

"arbitrum"

toChain

string

Yes

Destination chain identifier

"avax"

tokenIn

string

Yes

Input token identifier

"TBTC"

tokenOut

string

Yes

Output token identifier

"WETH"

amount

string

Yes

Human amount string

"100.00"

minAmountOut

string

Yes

Minimum output amount

"1"

timeInForce

string

No

GTC, GTD, IOC, or FOK

"GTC"

expiresAtMs

integer

No

Absolute expiry in ms since epoch

1745407200000

expireAfterMs

integer

No

Relative expiry in ms

86400000

network

string

No

mainnet or testnet

"mainnet"

slippageBps

integer

No

Quote-time slippage hint

75

recipient

string

No

Recipient address

"0x1234..."

Example

Responses

Code
Description

200

Replaced

400

Invalid request

401

Unauthorized

403

Forbidden

404

Not found

409

Order not replaceable or idempotency conflict

503

PG unavailable

Zert API — Replace Limit Order

Last updated