Endpoint for amending the price and/or max fillable count of an existing event-market order using the V2 request/response shape. The request count is the updated total/max fillable count, equal to already filled count plus desired resting remaining count. This behavior matches the v1 amend endpoints; only the request/response shape differs.
Documentation Index
Fetch the complete documentation index at: https://docs.kalshi.com/llms.txt
Use this file to discover all available pages before exploring further.
Your API key ID
RSA-PSS signature of the request
Request timestamp in milliseconds
Order ID
Subaccount number (0 for primary, 1-32 for subaccounts). Defaults to 0.
Market ticker
Side of the order
bid, ask Updated price for the order in fixed-point dollars.
"0.5600"
Updated total/max fillable count for the order. Set this to the order's already filled count plus the desired resting remaining count after the amend.
"10.00"
The original client-specified order ID to be amended
The new client-specified order ID after amendment
Identifier for an exchange shard. Defaults to 0 if unspecified. Note: currently only 0 supported.
0
Order amended successfully
Matching engine timestamp at which the amend was processed, as Unix epoch milliseconds.
Number of resting contracts remaining after the amend. This is the actual post-amend resting quantity, not the request's total/max fillable count. Only present when the amend caused a fill or changed the resting size.
"10.00"
Number of contracts filled as a result of the amend crossing the book. Only present when fills occurred or remaining size changed.
"10.00"
Volume-weighted average fill price for fills resulting from the amend. Only present when fills occurred.
"0.5600"
Volume-weighted average fee paid per contract for fills resulting from the amend. Only present when fills occurred.
"0.5600"