Exchange API Rate Limits and Order-Status Polling

Summary

This forum post asks how to monitor whether exchange limit orders have filled in a JavaScript trading loop. The example repeatedly requests the open and closed order list, checks for closed orders, logs fill details, and also processes webhook commands and stop-loss or take-profit actions. With a one-second loop interval, the platform reports an IP request-limit error and advises using a WebSocket for live updates instead of polling the API.

The post frames the practical issue as a conflict between frequent order-status checks and exchange rate limits. It does not include a confirmed fix or a response explaining how to integrate WebSocket updates, manage subscriptions, or recover from missed events. It therefore offers a useful operational warning rather than a complete implementation guide: polling order data too often can trigger limits, and the exchange-recommended streaming approach may be more suitable for timely updates. The code and reported error are specific to the author’s setup, so exact limits and available mechanisms depend on the exchange and platform.

Key ideas

• Repeatedly polling order status in a trading loop can exceed an exchange’s API request limit.
• The reported platform error recommends WebSocket updates for live data instead of API polling.
• The example loop also handles webhook commands and risk controls, but offers no completed WebSocket implementation.
• Rate limits and supported order-update mechanisms depend on the exchange and platform.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.