Skip to main content

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.

Properties

NameTypeDescriptionNotes
subaccountintOptional subaccount number to use for this amendment (0 for primary, 1-32 for subaccounts)[optional] [default to 0]
tickerstrMarket ticker
sidestrSide of the order
actionstrAction of the order
client_order_idstrThe original client-specified order ID to be amended[optional]
updated_client_order_idstrThe new client-specified order ID after amendment[optional]
yes_priceintUpdated yes price for the order in cents[optional]
no_priceintUpdated no price for the order in cents[optional]
yes_price_dollarsstrUS dollar amount as a fixed-point decimal string with up to 6 decimal places of precision. This is the maximum supported precision; valid quote intervals for a given market are constrained by that market’s price level structure.[optional]
no_price_dollarsstrUS dollar amount as a fixed-point decimal string with up to 6 decimal places of precision. This is the maximum supported precision; valid quote intervals for a given market are constrained by that market’s price level structure.[optional]
countintUpdated quantity for the order (whole contracts only). If updating quantity, provide count or count_fp; if both provided they must match.[optional]
count_fpstrFixed-point contract count string (2 decimals, e.g., "10.00"; referred to as "fp" in field names). Requests accept 0–2 decimal places (e.g., "10", "10.0", "10.00"); responses always emit 2 decimals. Fractional contract values (e.g., "2.50") are supported on markets with fractional trading enabled; the minimum granularity is 0.01 contracts. Integer contract count fields are legacy and will be deprecated; when both integer and fp fields are provided, they must match.[optional]