Rate Limits

TradersPost is NOT designed to be a high frequency trading platform. The minimum allowed timeframe to trade on is the 1 minute chart.

If you setup a strategy on anything less than the 1 minute chart or repeatedly violate the below rate limits, your account may be temporarily suspended or permanently banned if the issue is not addressed.

To ensure fair access and system integrity, please adhere to the following rate limits when using TradersPost webhooks:

Interval	Allowed Requests
1 Minute	60
1 Hour	500

When a webhook URL is rate-limited by TradersPost, it means the endpoint has received too many requests in a short time and has triggered a protective threshold. As a result, any additional requests to that webhook URL (from TradersPost) will receive an HTTP 429 Too Many Requests status code in the response and the response body will contain JSON that looks like the following.

{
    "success": false,
    "messageCode": "too-many-requests",
    "message": "Too Many Requests"
}

Exceeding these limits may result in temporary suspension or banning. Always monitor your strategies and the amount of webhooks being sent to TradersPost to prevent violations. If you have any questions about our rate limits, please contact us at [e-mail].

TradingView & TrendSpider Rate Limited

If you experience webhook rate limits when sending webhooks from third-party platforms like TradingView and TrendSpider, note that they might not notify you of failures directly in their interfaces. If you suspect rate limiting, contact TradingView or TrendSpider support for confirmation on whether TradersPost has limited your alert webhook

Broker Rate Limits

Brokers implement rate limits to ensure fair usage and system stability, alongside any limitations from TradersPost. These rules control request frequency to prevent overload and maintain responsiveness, providing equitable access for users. Understanding these policies is vital for optimizing trading system communication and preventing rejected requests due to

Broker	Rate Limit	Reference / Notes

Alpaca	200 requests per minute	Alpaca Docs

TradeStation	Not strictly published as a single number; historically ~10 requests/second in many endpoints	TradeStation Docs TradeStation dynamically applies rate limits. Exceeding limits typically returns 429 Too Many Requests.

Tradier	120 requests per minute (Basic); higher limits may apply for advanced/premium accounts	Tradier Docs

Robinhood	No explicit public number; unofficial sources suggest ~1 call/second and/or a broader per-minute limit	Robinhood Docs Official docs do not provide a hard numeric rate limit; behavior may vary across endpoints.

Tradovate	Enforced by a penalty system if you exceed short-term thresholds (e.g., ~10 requests/second)	Tradovate Docs Rate limits are enforced with increasing time penalties if exceeded.

Coinbase	Varies by endpoint; for Advanced Trade API, typically ~10 requests/second for private endpoints	Coinbase Docs Public endpoints and private endpoints often have different limits and “burst” rules.

E*TRADE	Not publicly documented	No official rate-limit statement available.

Bybit	Varies by API category (Spot, Futures, etc.); commonly cited ~50 requests/second in certain unified endpoints	Bybit Docs Rate limits differ depending on the endpoint type and “IP or account” categories.

Kraken	Varies; for Spot REST API, often ~15 calls in a 3-second window (i.e., ~5 calls/second)	Kraken Docs Additional tiers and advanced order endpoints may have different rules.

Binance	Uses “request weight” system (e.g., 1,200 weight per minute on many Spot endpoints)	Binance Docs Different endpoints consume different “weights.” Exceeding leads to 429 errors.

IBKR	Multiple “pacing violation” rules (e.g., ~50 messages/5 seconds), rather than a simple requests/minute threshold	IBKR Docs Rules vary between TWS API vs. Client Portal API. Exceeding triggers “pacing violation” lockouts.

Important Notes

1. Dynamic / Tiered Limits Some brokers apply multiple tiers or dynamic rules depending on the type of account, the specific endpoint (e.g., market data vs. trade placement), or your trading volume. Always confirm in the official documentation or by contacting the broker’s support.

2. “Burst” vs. “Sustained” Rate Even when a broker provides a requests-per-minute limit, there may be a secondary per-second or per-burst threshold that can trigger errors if exceeded in short bursts.

3. Penalties / Lockouts Many brokers return HTTP status code 429 (Too Many Requests) if you exceed the limit, and some impose temporary lockouts (“cool-down” periods) or progressively longer penalties for repeated excesses.