updateSlippageSetting action sets the market-order slippage cap for your account within a market deployer, expressed in basis points. Market orders are priced from the mark price plus or minus this allowance, so the cap bounds how far a market order may execute from the current mark.
The setting is scoped to the pair (account, market deployer) — it is not per-contract, and one call covers every contract under that deployer. The default is 1000 bps (10%). Your accountId is recovered from the signature.
Endpoint
Request
Action fields
string
required
Fixed value:
"updateSlippageSetting".int32
required
The market deployer this setting applies to. You must already be enrolled in it.
int
required
The market-order slippage cap in basis points. Valid range is
(0, 10000], where 10000 equals 100%. Values outside this range are rejected. Defaults to 1000 (10%) when never set.Response
Success
Rejection
Rejections still return HTTP 200 withstatus: "ok". A rejected request carries a non-zero errorCode and an errorMessage inside response.data, and both marketSlippageBpsBefore and marketSlippageBpsAfter are 0.
A non-zero
errorCode means the request was refused and the slippage setting is unchanged. Check for it on every call — status: "ok" alone does not mean the setting was applied.Response fields
int
The cap in effect before this call. Returns
0 on rejection.int
The cap in effect after this call. Returns
0 on rejection.int
Present only on rejection. Identifies the failure reason.
string
Present only on rejection. Human-readable description of the failure.
Errors
Reading the current value
The cap in effect is returned asmarketSlippageBps by the userAccount query — the same field this action writes. Read it back there rather than caching the value locally.