2026-06-16 · Kalshi · 46 条相关讨论
For migrating to v2, isn't `create_order`supposed to use `outcome_side` and `book_side` or am I missing something? https://docs.kalshi.com/api-reference/orders/create-order-v2
For migrating to v2, isn't `create_order`supposed to use `outcome_side` and `book_side` or am I missing something? https://docs.kalshi.com/api-reference/orders/create-order-v2
Is it only for `get_order`? https://docs.kalshi.com/api-reference/orders/get-order#get-order
Is it only for `get_order`? https://docs.kalshi.com/api-reference/orders/get-order#get-order
create order v2 currently uses "side", but that's an interesting point; I can add a synonym for book_side or something like that
create order v2 currently uses "side", but that's an interesting point; I can add a synonym for book_side or something like that
I think that `side` being limited to `bid` and `ask` is self-explanatory. Maybe you just could add something to the documentation instead of adding a new field/property.
I think that `side` being limited to `bid` and `ask` is self-explanatory. Maybe you just could add something to the documentation instead of adding a new field/property.
Your API, your design but for clarity's sake, I would recommend not including two different options for saying the same thing in the API. The use of outcome_side and book_side simulataneously just serves to confuse and make the API marginally less efficient. I quite like that the create order endpoint is slimmed to the essentials and users can always translate between book/outcome side conceptions on their own end
Your API, your design but for clarity's sake, I would recommend not including two different options for saying the same thing in the API. The use of outcome_side and book_side simulataneously just serves to confuse and make the API marginally less efficient. I quite like that the create order endpoint is slimmed to the essentials and users can always translate between book/outcome side conceptions on their own end
So I'm in the process of moving to v2, am I correct in thinking that only the get endpoints need to be changed? And only how responses are handled? i.e. payloads don't need to be modified
So I'm in the process of moving to v2, am I correct in thinking that only the get endpoints need to be changed? And only how responses are handled? i.e. payloads don't need to be modified
I just realized this lol
I just realized this lol
https://tenor.com/view/hello-anyone-there-hello-hi-waving-funny-hello-gif-3743946199014517529
https://tenor.com/view/hello-anyone-there-hello-hi-waving-funny-hello-gif-3743946199014517529
the payloads are slightly different
the payloads are slightly different
For which endpoint
For which endpoint
Also I'm talking about request payload*
Also I'm talking about request payload*
I know repsonse payload is different
I know repsonse payload is different
the request is slightly different too
the request is slightly different too
For which endpoint o_O
For which endpoint o_O
create, at least, don't know the others off the top of my head but would recommend just checking
create, at least, don't know the others off the top of my head but would recommend just checking
Wait is there no way now to tell if an order is a buy or sell?
Wait is there no way now to tell if an order is a buy or sell?
read the docs
read the docs
Yeah, and I didn't see anything talking about how to determine once `action` is removed
Yeah, and I didn't see anything talking about how to determine once `action` is removed
buy yes = sell no. sell yes = buy no. since v2, api users can no longer use the 'no'-oriented view; that is a privilege reserved for ui users. yes it is annoying if you're used to thinking in terms of 'no', no they're not going to change it
buy yes = sell no. sell yes = buy no. since v2, api users can no longer use the 'no'-oriented view; that is a privilege reserved for ui users. yes it is annoying if you're used to thinking in terms of 'no', no they're not going to change it
you don't seem to have your head around the point of the v2 migration
you don't seem to have your head around the point of the v2 migration