该用户的聊天记录定位。
I recall this comment from James, seems like the batch concept might be on the way out. I proactively removed support from my system. https://discord.com/channels/871819895443189862/927686720990892032/1511791137298452500
I recall this comment from James, seems like the batch concept might be on the way out. I proactively removed support from my system. https://discord.com/channels/871819895443189862/927686720990892032/1511791137298452500
The `outcome_side` field sounds similar to user intent?
The `outcome_side` field sounds similar to user intent?
yeah I'm sure others have a better handle on it, I'm pretty newbie
yeah I'm sure others have a better handle on it, I'm pretty newbie
I've run into this kind of confusion between API intent and the web UI. Personally I've tried to switch things up to just deal with YES only, since it seems from the recent changes that this is the framing going forward https://docs.kalshi.com/getting_started/order_direction. I don't have a clearer explanation to give than to squint at the docs and get help from your favorite AI
I've run into this kind of confusion between API intent and the web UI. Personally I've tried to switch things up to just deal with YES only, since it seems from the recent changes that this is the framing going forward https://docs.kalshi.com/getting_started/order_direction. I don't have a clearer explanation to give than to squint at the docs and get help from your favorite AI
seems to be pulled from: `https://api.elections.kalshi.com/v1/users/{id}/api_usage_level/volume_progress`
seems to be pulled from: `https://api.elections.kalshi.com/v1/users/{id}/api_usage_level/volume_progress`
huh weird! Maybe some glitch given you have some other tabs as well that aren't on mine
huh weird! Maybe some glitch given you have some other tabs as well that aren't on mine
I see it in the web porfolio UI here. Click on the current tier and progress bar appears at the top of popup.
I see it in the web porfolio UI here. Click on the current tier and progress bar appears at the top of popup.
agreed it does vary by endpoint, I was just observing that our baseline raw latency is under 5. Kalshi's processing can add significant more but unless those pipelines were wholly different for a different API surface than REST, we would expect similar
agreed it does vary by endpoint, I was just observing that our baseline raw latency is under 5. Kalshi's processing can add significant more but unless those pipelines were wholly different for a different API surface than REST, we would expect similar
OK, seems to be ~7ms currently but I've observed less
OK, seems to be ~7ms currently but I've observed less
``` host:~$ curl -o /dev/null -s -w '%{time_total}s\n' https://external-api.kalshi.com/trade-api/v2/exchange/status 0.007356s ```
``` host:~$ curl -o /dev/null -s -w '%{time_total}s\n' https://external-api.kalshi.com/trade-api/v2/exchange/status 0.007356s ```
When I curl `https://external-api.kalshi.com/trade-api/v2/exchange/status` from my host, it is <5ms consistently. No magic
When I curl `https://external-api.kalshi.com/trade-api/v2/exchange/status` from my host, it is <5ms consistently. No magic
I see <5ms through the REST `external-api` endpoints, so it couldn't be that
I see <5ms through the REST `external-api` endpoints, so it couldn't be that
nice, its a good idea. I've been thinking for a while I need something automated to watch for changes, thanks for the inspiration
nice, its a good idea. I've been thinking for a while I need something automated to watch for changes, thanks for the inspiration
tha'ts handy...is this homegrown or something available to watch?
tha'ts handy...is this homegrown or something available to watch?
No, wasn't aware of that. Just `subscribe` command with desired `channels` and `market_tickers`
No, wasn't aware of that. Just `subscribe` command with desired `channels` and `market_tickers`
Resolved for me after code changes. Seems like something changed with the websocket subscribe behavior, but I suppose I can't prove it. Unless I'm crazy, when subscribing to `orderbook_delta` for multiple tickers: Before: Kalshi’s ACK identified the market directly by echoing the ticker list. Now: Kalshi’s ACK may identify the request only indirectly, through the WebSocket command id; the ticker has to be inferred from the command the client sent.
Resolved for me after code changes. Seems like something changed with the websocket subscribe behavior, but I suppose I can't prove it. Unless I'm crazy, when subscribing to `orderbook_delta` for multiple tickers: Before: Kalshi’s ACK identified the market directly by echoing the ticker list. Now: Kalshi’s ACK may identify the request only indirectly, through the WebSocket command id; the ticker has to be inferred from the command the client sent.
external-api
external-api
I'm not seeing 503, just not establishing the feed
I'm not seeing 503, just not establishing the feed
my system is no longer successfully subscribing to orderbook WS since about 2 hours ago. Not sure if something changed in the behavior, currently troubleshooting. Manual test with `websocat` worked albeit possibly with different sequencing than before
my system is no longer successfully subscribing to orderbook WS since about 2 hours ago. Not sure if something changed in the behavior, currently troubleshooting. Manual test with `websocat` worked albeit possibly with different sequencing than before
Kalshi