I'm running into an issue with my app when using websocket for book updates, where a massive trade that flips several rows from bids to asks at once will cause those rows to sort of glitch out and get stuck in an in-between state, either showing empty or many of them still showing up as though they have bids on them. Has anyone experienced a similar issue before? If so how'd you address it?
I'm running into an issue with my app when using websocket for book updates, where a massive trade that flips several rows from bids to asks at once will cause those rows to sort of glitch out and get stuck in an in-between state, either showing empty or many of them still showing up as though they have bids on them. Has anyone experienced a similar issue before? If so how'd you address it?
I'd put money on your implementation dropping deltas somehow - but ooc which markets are you seeing this on?
I'd put money on your implementation dropping deltas somehow - but ooc which markets are you seeing this on?
it can happen on any market seemingly, but most often on live sports matches
it can happen on any market seemingly, but most often on live sports matches
Make sure you're monitoring seq values and pulling a new snapshot if there's ever a gap
Make sure you're monitoring seq values and pulling a new snapshot if there's ever a gap
That's almost certainly on your end if you're seeing it repeatedly across many markets
That's almost certainly on your end if you're seeing it repeatedly across many markets
You might have a caching issue since seq gaps are also pretty rare
You might have a caching issue since seq gaps are also pretty rare
alright that makes sense, appreciate it
alright that makes sense, appreciate it
im getting the "INCORRECT_API_KEY_SIGNATURE"
im getting the "INCORRECT_API_KEY_SIGNATURE"
error
error
how ever its getting my balance correctly
how ever its getting my balance correctly
Can you get orders, positions, etc.?
Can you get orders, positions, etc.?
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?
I'm switching over from V1 to V2 orders. Now when I place a "buy NO" order via the V2 endpoint (as side: ask), the Kalshi UI displays it as "Sell Yes." I understand these are economically equivalent — just wondering if there's any way to submit it so it reflects as a "Buy NO". It's slightly confusing because I don't have any YES contracts to sell.
I'm switching over from V1 to V2 orders. Now when I place a "buy NO" order via the V2 endpoint (as side: ask), the Kalshi UI displays it as "Sell Yes." I understand these are economically equivalent — just wondering if there's any way to submit it so it reflects as a "Buy NO". It's slightly confusing because I don't have any YES contracts to sell.
no
no
think of it as selling them short
think of it as selling them short
Yeah, I figured that's what I'll have to train myself to do.
Yeah, I figured that's what I'll have to train myself to do.
anyone feel like being charitable? I've been out for over a month because of life and etc, my bots been shut off and I haven't updated anything since. going back over the change log trying to get a measure of what needs updated, doesn't look too bad, really I think for me I just to change to /portfolio/events/orders endpoint and change to the new order direction semantics. Anything else to be aware of?
anyone feel like being charitable? I've been out for over a month because of life and etc, my bots been shut off and I haven't updated anything since. going back over the change log trying to get a measure of what needs updated, doesn't look too bad, really I think for me I just to change to /portfolio/events/orders endpoint and change to the new order direction semantics. Anything else to be aware of?
anyone’s else script working really well on weekdays but weekend it just sucks?
anyone’s else script working really well on weekdays but weekend it just sucks?
Wondering how to fix the problem of the floor_strike endpoint for certain markets being empty when I make a REST API pull?
Wondering how to fix the problem of the floor_strike endpoint for certain markets being empty when I make a REST API pull?