R.R.参与话题 1消息总数 6

R.R. 2026-06-11 22:24:58 ↗ Kalshi

Got it. Sadly the throttle was released during a few big losing trades QQ. But thanks for the reply 👍🏽

Got it. Sadly the throttle was released during a few big losing trades QQ. But thanks for the reply 👍🏽

R.R. 2026-06-11 21:35:13 ↗ Kalshi

Overnight it looks like it did for me. I went from not being able to execute 2 writes/sec because of the 10x throttle, to, being able to execute those 2 writes/sec...

Overnight it looks like it did for me. I went from not being able to execute 2 writes/sec because of the 10x throttle, to, being able to execute those 2 writes/sec...

R.R. 2026-06-10 22:22:27 ↗ Kalshi Kalshi API v2迁移引发429限流与端点困惑

You are officially smarter than Claude who could not debug this despite 2 hours of debugging. Thank you!

You are officially smarter than Claude who could not debug this despite 2 hours of debugging. Thank you!

R.R. 2026-06-10 22:18:05 ↗ Kalshi Kalshi API v2迁移引发429限流与端点困惑

Got it. Also, my code points to https://api.elections.kalshi.com/trade-api/v2/portfolio/orders Is that the correct endpoint or is there a newer one?

Got it. Also, my code points to https://api.elections.kalshi.com/trade-api/v2/portfolio/orders Is that the correct endpoint or is there a newer one?

R.R. 2026-06-10 22:14:39 ↗ Kalshi

Thanks for your help. I'll look into it once my Claude budget resets 😂😭

Thanks for your help. I'll look into it once my Claude budget resets 😂😭

R.R. 2026-06-10 22:01:41 ↗ Kalshi Kalshi API v2迁移引发429限流与端点困惑

Hi - Getting 50% 429s on order placement despite being well under documented rate limits Tier: Basic (confirmed via GET /account/limits — write refill=100/s, capacity=100) I'm placing IOC limit orders via POST /portfolio/orders on api.elections.kalshi.com at ~2 orders/sec (hardcoded 0.5s throttle). That's 20 tokens/sec against a 100 tokens/sec budget. No retries, no other write endpoints, no batch calls. Single script, single API key. Roughly 50% of orders return 429 too_many_requests. The failures come in sustained bursts (e.g. 17 consecutive 429s at ~1/sec) while other orders in the same window succeed. Example window: 2026-06-10 10:35:00–10:45:00 UTC, ticker KXBTC15M-26JUN100645-45. 104 order attempts, 54 filled, 50 returned 429. Is there an additional rate limit beyond the token bucket (per-market, per-endpoint, gateway-level)? Or something else that could be draining my write bucket? Happy to share my key ID via DM if that helps look up the bucket history.

Hi - Getting 50% 429s on order placement despite being well under documented rate limits Tier: Basic (confirmed via GET /account/limits — write refill=100/s, capacity=100) I'm placing IOC limit orders via POST /portfolio/orders on api.elections.kalshi.com at ~2 orders/sec (hardcoded 0.5s throttle). That's 20 tokens/sec against a 100 tokens/sec budget. No retries, no other write endpoints, no batch calls. Single script, single API key. Roughly 50% of orders return 429 too_many_requests. The failures come in sustained bursts (e.g. 17 consecutive 429s at ~1/sec) while other orders in the same window succeed. Example window: 2026-06-10 10:35:00–10:45:00 UTC, ticker KXBTC15M-26JUN100645-45. 104 order attempts, 54 filled, 50 returned 429. Is there an additional rate limit beyond the token bucket (per-market, per-endpoint, gateway-level)? Or something else that could be draining my write bucket? Happy to share my key ID via DM if that helps look up the bucket history.