该用户的聊天记录定位。
Only "sell no" orders display as buys. And I half agree with you - displaying adding vs covering would be useful. It's just not unreasonable to expect us to be tracking that on our own anyway.
Only "sell no" orders display as buys. And I half agree with you - displaying adding vs covering would be useful. It's just not unreasonable to expect us to be tracking that on our own anyway.
There's a flag set somewhere (sure, in the backend) specifically for the frontend: show the user their position this way
There's a flag set somewhere (sure, in the backend) specifically for the frontend: show the user their position this way
api doesn't have all the features the frontend does, not backend
api doesn't have all the features the frontend does, not backend
Ok, I guess I just see it as having much more utility with a taker order as it can just cancel the remainder. With a resting, it's like hey dumdum you don't have that many.
Ok, I guess I just see it as having much more utility with a taker order as it can just cancel the remainder. With a resting, it's like hey dumdum you don't have that many.
What would you expect to happen if you're long 40 contracts and you place a reduce-only resting sell for 50 contracts?
What would you expect to happen if you're long 40 contracts and you place a reduce-only resting sell for 50 contracts?
Yeah, I do wish there were an indicator of adding/covering a position but that's easy to calc on your own.
Yeah, I do wish there were an indicator of adding/covering a position but that's easy to calc on your own.
It's for the normies.
It's for the normies.
I would argue the api is more sensible. There is only 1 book, and the api now accurately portrays that.
I would argue the api is more sensible. There is only 1 book, and the api now accurately portrays that.
Yeah it closes it. Sell no = buy yes.
Yeah it closes it. Sell no = buy yes.
Because you're buying yes. You can only enter orders from the yes perspective thru the api.
Because you're buying yes. You can only enter orders from the yes perspective thru the api.
Correct. Just think of it like you sold yes short at 10c.
Correct. Just think of it like you sold yes short at 10c.
You can only buy and sell yes via api (including sell to open)
You can only buy and sell yes via api (including sell to open)
I've been running all day with no issues - are you guys using the external-api or elections host? (i'm on external)
I've been running all day with no issues - are you guys using the external-api or elections host? (i'm on external)
Could I have permanent expert as a consolation prize for filing out the advanced application the day before the auto-upgrade endpoint was announced pretty please?
Could I have permanent expert as a consolation prize for filing out the advanced application the day before the auto-upgrade endpoint was announced pretty please?
Create v2 just returns the single price. Pretty easy to calc no_price if you need it for some reason.
Create v2 just returns the single price. Pretty easy to calc no_price if you need it for some reason.
So did you stop charing pnl when you crossed 7 figures or 8?
So did you stop charing pnl when you crossed 7 figures or 8?
sounded like they are processed faster if sent individually (in parallel of course)
sounded like they are processed faster if sent individually (in parallel of course)
sounded like no
sounded like no
also not an answer to your question but icymi james indicated the batch endpoints are likely going away in the near future
also not an answer to your question but icymi james indicated the batch endpoints are likely going away in the near future
it's in milestones
it's in milestones
Look at milestones (pass the event ticker)
Look at milestones (pass the event ticker)
I sub to ~30k and have not seen that error
I sub to ~30k and have not seen that error
can still cancel though
can still cancel though
yep
yep
but not create
but not create
able to cancel now
able to cancel now
Anyone else unable to cancel or amend web or api?
Anyone else unable to cancel or amend web or api?
https://docs.kalshi.com/changelog#may-5-2026
https://docs.kalshi.com/changelog#may-5-2026
think of it as selling them short
think of it as selling them short
no
no
If you can get your balance, you're signing that one correctly. How are you signing your other requests differently?
If you can get your balance, you're signing that one correctly. How are you signing your other requests differently?
Can you get orders, positions, etc.?
Can you get orders, positions, etc.?
also maybe don't share your full key id
also maybe don't share your full key id
https://docs.kalshi.com/changelog#june-4-2026 <@1452712865940373785>
https://docs.kalshi.com/changelog#june-4-2026 <@1452712865940373785>
https://docs.kalshi.com/api-reference/account/list-non-default-endpoint-costs
https://docs.kalshi.com/api-reference/account/list-non-default-endpoint-costs
Order V2 (in API V2) has docs at the bottom of the orders section with V2 in their name. I don't see the quickstart updated if that's what you meant.
Order V2 (in API V2) has docs at the bottom of the orders section with V2 in their name. I don't see the quickstart updated if that's what you meant.
It contains the client_order_id, not order_id
It contains the client_order_id, not order_id
Those are the old ("v1") endpoints https://docs.kalshi.com/changelog#apr-22-2026-2 https://docs.kalshi.com/changelog#may-25-2026 <@1308963072429527122>
Those are the old ("v1") endpoints https://docs.kalshi.com/changelog#apr-22-2026-2 https://docs.kalshi.com/changelog#may-25-2026 <@1308963072429527122>
Kalshi