Anyone know how to accurately calculate realized PNL and current avg price?
Anyone know how to accurately calculate realized PNL and current avg price?
2026-06-22 · Kalshi · 24 条相关讨论
Anyone know how to accurately calculate realized PNL and current avg price?
Anyone know how to accurately calculate realized PNL and current avg price?
Is there somewhere else to fetch `position_fee_cost_dollars` on initial load besides waiting for websocket updates?
Is there somewhere else to fetch `position_fee_cost_dollars` on initial load besides waiting for websocket updates?
Bc it seems like that's what's causing the discrepancy
Bc it seems like that's what's causing the discrepancy
Pls help 😭
Pls help 😭
I don't like seeing this avg price
I don't like seeing this avg price
The msg right above that
The msg right above that
I'm asking here...
I'm asking here...
https://tenor.com/view/a4c712-dashera4c-nonchalant-gamer-i%27m-speechless-speechless-gif-13022095084831385298
https://tenor.com/view/a4c712-dashera4c-nonchalant-gamer-i%27m-speechless-speechless-gif-13022095084831385298
Why does create order return `remaining_count`, but get order return `remaining_count_fp`, despite both using the same format?
Why does create order return `remaining_count`, but get order return `remaining_count_fp`, despite both using the same format?
CAN THIS BE STANDARDIZED???
CAN THIS BE STANDARDIZED???
It was part of the fixed point migration a few months back. They were returning parallel values in different formats to make the transition easier. Still some artifacts remaining
It was part of the fixed point migration a few months back. They were returning parallel values in different formats to make the transition easier. Still some artifacts remaining
Moving forward, what format are they going to use? So I can migrate in advance
Moving forward, what format are they going to use? So I can migrate in advance
_fp and _dollars? or without them
_fp and _dollars? or without them
Expect new properties on new types to use the fixed point representation and to not need the _fp or _dollars suffix to disambiguate, because they won't have both forms.
Expect new properties on new types to use the fixed point representation and to not need the _fp or _dollars suffix to disambiguate, because they won't have both forms.
Anyone know if the documentation for this is outdated? https://docs.kalshi.com/margin-ws/websockets/user-orders#user-orders Or if that's the response format moving forward
Anyone know if the documentation for this is outdated? https://docs.kalshi.com/margin-ws/websockets/user-orders#user-orders Or if that's the response format moving forward
There's a couple of fields I'm seeing differences in
There's a couple of fields I'm seeing differences in
- docs doesn't have book_side - side is different enum - docs doesn't have is_yes (ik this is deprecated) - docs doesn't have status - docs lacking taker fees - docs lacking last_update_time - docs has fill_count, api has fill_count_fp (same with remaining count and initial count)
- docs doesn't have book_side - side is different enum - docs doesn't have is_yes (ik this is deprecated) - docs doesn't have status - docs lacking taker fees - docs lacking last_update_time - docs has fill_count, api has fill_count_fp (same with remaining count and initial count)
Oh wait
Oh wait
Nvm I was looking at margin exchange docs
Nvm I was looking at margin exchange docs
lel
lel