Support Board
Date/Time: Wed, 05 Feb 2025 10:47:41 +0000
Post From: Wrong conclusion: Bitmex - reconnects in a loop with latest Sierra Chart
[2020-03-08 11:46:40] |
DRand444 - Posts: 3 |
Yes, what I meant to ask is why I'm getting a 429 HTTP status code from Bitmex when Sierra Chart is the only application I am connecting to with my API key? That code is sent when API ratelimits are being exceeded. I have tried changing my IP address, shutting down Sierra Chart for an hour, and starting it again. I have the same issue. Can I provide further information for you to troubleshoot? Rate Limits
The following actions are ratelimited: Subscription: Consumes one token from your request limiter. Connection: 20 per hour, on a separate limiter. Dead Man’s Switch (cancelAllAfter): Consumes one token from your request limiter. If you exceed your ratelimit on a subscription or cancelAllAfter call, you will see a message like: {"status":429,"error":"Rate limit exceeded, retry in 1 seconds.","meta":{"retryAfter":1},"request":{"op":"subscribe","args":"orderBook"}} If you are ratelimited from connecting, the message is slightly different (example includes headers): HTTP/1.1 429 Too Many Requests Cache-Control: no-store, no-cache, must-revalidate, max-age=0 Pragma: no-cache X-RateLimit-Limit: 20 X-RateLimit-Remaining: 0 X-RateLimit-Reset: 1506983924 Retry-After: 29 Content-Type: application/json Content-Length: 55 Date: Mon, 02 Oct 2017 21:43:49 GMT Connection: keep-alive {"error":"Rate limit exceeded, retry in 29 seconds."} Date Time Of Last Edit: 2020-03-08 11:47:25
|