KalshiHave you tried GetPositions in prod? No sense troubleshooting an issue if it only exists in demo.
Have you tried GetPositions in prod? No sense troubleshooting an issue if it only exists in demo.
Arbgame参与话题 17消息总数 88
该用户的聊天记录定位。
聊天记录
共 88 条，显示第 1-50 条I guess the exception is if someone enters a position via the web, it will be accurate since you can't sell to open there.
I guess the exception is if someone enters a position via the web, it will be accurate since you can't sell to open there.
I'm pretty sure it does show the taker action
I'm pretty sure it does show the taker action
Nope. That "bought yes" could have been the taker entering a yes position or exiting a no position.
Nope. That "bought yes" could have been the taker entering a yes position or exiting a no position.
But even that doesn't tell you. It just tells you how the order was entered, not whether they're entering vs exiting a position.
But even that doesn't tell you. It just tells you how the order was entered, not whether they're entering vs exiting a position.
No but there wasn't before either. You can look at change in open interest to get an idea.
No but there wasn't before either. You can look at change in open interest to get an idea.
It still has taker_side and now the new book_side and outcome_side too
It still has taker_side and now the new book_side and outcome_side too
there's no such thing as no's
there's no such thing as no's
No. A 90c ask for "yes" and a 10c bid for "no" are exactly the same order. https://docs.kalshi.com/getting_started/order_direction
No. A 90c ask for "yes" and a 10c bid for "no" are exactly the same order. https://docs.kalshi.com/getting_started/order_direction
yeah that's what I see from web and api, what does your ask look like?
yeah that's what I see from web and api, what does your ask look like?
why would it match now then?
why would it match now then?
Are you requesting a snapshot and it's not matching what you see on the web?
Are you requesting a snapshot and it's not matching what you see on the web?
Hadn't used expiration time before but just tested and yeah works for me too
Hadn't used expiration time before but just tested and yeah works for me too
Worth a try omitting it.
Worth a try omitting it.
Does it reject it if you omit time_in_force?
Does it reject it if you omit time_in_force?
Yep it definitely works. It still sends "yes":[.../"no":[... verbiage, but the "no" prices are converted to yes.
Yep it definitely works. It still sends "yes":[.../"no":[... verbiage, but the "no" prices are converted to yes.
Ah I forgot that changed. Does it go through if you remove the expiration time and leave everything else the same?
Ah I forgot that changed. Does it go through if you remove the expiration time and leave everything else the same?
Why would you send both?
Why would you send both?
dozens, but only a handful of patterns
dozens, but only a handful of patterns
It's always the "yes" price. There is no such thing as a "no" side as far as the create order endpoint is concerned.
It's always the "yes" price. There is no such thing as a "no" side as far as the create order endpoint is concerned.
I've seen the same trades show up in both the historical and current endpoints simultaneously, forget if they were just before or just after the cutoff
I've seen the same trades show up in both the historical and current endpoints simultaneously, forget if they were just before or just after the cutoff
actually not phantom, just wouldn't have any effect
actually not phantom, just wouldn't have any effect
definitely not gtc - that'd be a phantom order
definitely not gtc - that'd be a phantom order
Yeah was trying to figure out exactly the intent. That would be true for a buy but describes a limit for a sell. It would essentially be a "stop loss cancel".
Yeah was trying to figure out exactly the intent. That would be true for a buy but describes a limit for a sell. It would essentially be a "stop loss cancel".
Wouldn't that be a limit price?
Wouldn't that be a limit price?
Yikes, sounds like this goes deeper.
Yikes, sounds like this goes deeper.
It seems like the only reason to have an optional client_order_id in the amend request would be to reject a no-match if the client uses that field. You're saying you're passing one, it reports no-match, but amends anyway?
It seems like the only reason to have an optional client_order_id in the amend request would be to reject a no-match if the client uses that field. You're saying you're passing one, it reports no-match, but amends anyway?
Seems back to normal now. I've been seeing ws latency spikes throughout the day too.
Seems back to normal now. I've been seeing ws latency spikes throughout the day too.
getting websocket disconnects and http timeouts
getting websocket disconnects and http timeouts
or you could just look at the yes bid
or you could just look at the yes bid
If you mean looking to buy no, then you are correct. But try to think of that as selling yes and it will be much simpler.
If you mean looking to buy no, then you are correct. But try to think of that as selling yes and it will be much simpler.
I was surprised setting that flag didn't also return book sides as "bid_dollars_fp": [...
I was surprised setting that flag didn't also return book sides as "bid_dollars_fp": [...
If you're wanting to trade with that 9c order then the price is 9 cents
If you're wanting to trade with that 9c order then the price is 9 cents
feels a bit like watching bitcoin 10 yr ago
feels a bit like watching bitcoin 10 yr ago
I haven't been doing this that long and when I started there were ~5k markets open at any given time
I haven't been doing this that long and when I started there were ~5k markets open at any given time
https://docs.kalshi.com/getting_started/quick_start_websockets#complete-example
https://docs.kalshi.com/getting_started/quick_start_websockets#complete-example
Sorry to hear it. Out of curiosity, do you see the same error after getting that email?
Sorry to hear it. Out of curiosity, do you see the same error after getting that email?
1. It would be most helpful to see the actual request body you are sending 2. Make sure toFixed() returns a string 3. Try simplifying your client order id to something that only contains letters, numbers, and dashes
1. It would be most helpful to see the actual request body you are sending 2. Make sure toFixed() returns a string 3. Try simplifying your client order id to something that only contains letters, numbers, and dashes
I think we've seen that error before for completely unrelated issues iirc
I think we've seen that error before for completely unrelated issues iirc
Looks like they're not even submitting it fok though.
Looks like they're not even submitting it fok though.
You (or your helper) invented the intent param, and price and count should be strings.
You (or your helper) invented the intent param, and price and count should be strings.
I'd pay 75c for they're not shadow banning.
I'd pay 75c for they're not shadow banning.
look at milestones
look at milestones
Just gonna have to make your own dashboard I guess. Which if you're using the api should be pretty trivial.
Just gonna have to make your own dashboard I guess. Which if you're using the api should be pretty trivial.
You do have to know what you have beforehand for the order to make sense - but if you do you know exactly what the order is doing - agreed?
You do have to know what you have beforehand for the order to make sense - but if you do you know exactly what the order is doing - agreed?
Doesn't depend on how any order was placed, it depends on your position.
Doesn't depend on how any order was placed, it depends on your position.
If you abandon the idea of there being any such thing as a "no" side it's dramatically simpler.
If you abandon the idea of there being any such thing as a "no" side it's dramatically simpler.
How so?
How so?
But buying yes and selling no are exactly the same action. There is no difference in the backend.
But buying yes and selling no are exactly the same action. There is no difference in the backend.
It's only in the backend to facilitate frontend display. Every order is either a bid or an ask. There is no "no". But I'm sure I'm biased. I was converting everything to "yes" on ingest since I started. So I've been dealing with the whole "this is an offer but I have to mentally convert to a 'no' bid" when using the mobile site from the outset.
It's only in the backend to facilitate frontend display. Every order is either a bid or an ask. There is no "no". But I'm sure I'm biased. I was converting everything to "yes" on ingest since I started. So I've been dealing with the whole "this is an offer but I have to mentally convert to a 'no' bid" when using the mobile site from the outset.
第 1 / 2 页
下一页 →