Kalshiyea also gives you more accurate fills
yea also gives you more accurate fills
Evan参与话题 2消息总数 7
该用户的聊天记录定位。
聊天记录
共 7 条，显示第 1-7 条you have to use the sample passport in the presentation slide and then scan your face
you have to use the sample passport in the presentation slide and then scan your face
no should be immediate
no should be immediate
seems like Kalshi's own vendor SDK reproduces the 403, so it can't be our code; the same key/signer gets REST 200 but WS 403 from two different ips, seems specific to ws auth
seems like Kalshi's own vendor SDK reproduces the 403, so it can't be our code; the same key/signer gets REST 200 but WS 403 from two different ips, seems specific to ws auth
no, i'm in the US
no, i'm in the US
Hey, looking for some help on API usage. I was using websockets and suddenly a couple weeks back I started getting 403 errors on all websocket access. I talked to Kalshi AI support, it said it was manually revoked and must be manually reviewed. How can I get in touch with someone to help me lift the restriction?
Hey, looking for some help on API usage. I was using websockets and suddenly a couple weeks back I started getting 403 errors on all websocket access. I talked to Kalshi AI support, it said it was manually revoked and must be manually reviewed. How can I get in touch with someone to help me lift the restriction?
Hi, My production account gets websocket_access_blocked on wss://external-api-ws.kalshi.com while REST works and demo ws works. Why, and how do I restore it? My old api key died ~Jun 3, may it be due to request volume? I was requesting 1/sec on basic but now switched to advanced
Hi, My production account gets websocket_access_blocked on wss://external-api-ws.kalshi.com while REST works and demo ws works. Why, and how do I restore it? My old api key died ~Jun 3, may it be due to request volume? I was requesting 1/sec on basic but now switched to advanced