API Rate Limits: How Broker Throttling Kills Retail Bots

Your Trading Bot Isn't Broken. Your Broker Is Killing It.

Your EA sends a market order at 2:15 PM. The broker receives it. The API call gets queued. By the time your order executes, the price is 20 pips away from where you wanted it. You blame the bot. The bot isn't the problem.

Brokers enforce API rate limits—hard caps on how many requests you can send per second. Retail accounts get 10-50 requests/second. Enterprise accounts get 1,000+. When your bot hits the limit during a news spike or earnings gap, every additional order gets rejected or queued until the next second. By then, the move is over.

This isn't a bug. It's by design. And it's costing you fills.

Why Brokers Throttle Retail Traders

Brokers claim rate limiting protects their infrastructure. That's partially true. A single retail bot making 500 requests per second could crash their order processing system. But that's not the real reason they throttle you.

The real reason: retail traders are liabilities. If your bot generates losses, the broker eats the cost of margin calls, hedging, and failed liquidations. If your bot wins too consistently, the broker loses money on the spread. Either way, they want to slow you down.

Enterprise traders run through prime brokers. Prime brokers have skin in the game—they profit from your execution quality, not from your failure. So they don't throttle. They optimize. Your orders get routed through multiple exchanges, split across dark pools, and executed with millisecond precision. Your limit orders execute faster. Your market orders get better fills.

Retail traders on retail brokers? You get the leftover infrastructure.

When Do Retail Bots Hit the Rate Limit?

Rate limits feel invisible until volatility hits.

When the Fed announces a rate decision, oil crashes 10%, or a major stock reports earnings, thousands of retail bots all send orders at the same second. Brokers' API systems queue the requests. Your bot sends order #1 at 2:00:00.001. The broker processes it at 2:00:00.050. Your bot sends order #2 at 2:00:00.002. The broker queues it. By 2:00:00.100, your bot has hit the rate limit and gets rejected responses for all further orders until 2:00:01.000.

You miss the move. The opportunity closes. Your bot sits idle for a second while the market moves 50 pips.

This happens more during:

• Economic data releases (employment, inflation, GDP)—2-3 second windows where algos trade first
• Earnings announcements—stocks gap up/down 5-10% in milliseconds
• Central bank decisions—correlations shift, volatility spikes
• Market opens/closes—volume concentrates in first/last 60 seconds
• Flash crashes—everyone exits at once, your orders queue behind 100K others

During these windows, you don't get throttled because your bot is aggressive. You get throttled because everyone is aggressive and brokers can't handle the load.

The Real Cost of Throttling

Slippage from rate limits costs more than you think.

Let's say your bot is designed to scalp 10 pips per trade, 5 times per session. Normal session: you execute 5 trades, make 50 pips. During volatile sessions when rate limits hit, 2 of your 5 orders get delayed. The delayed orders execute 20 pips worse than intended. Instead of +50 pips, you get +10 pips. You just lost 80% of your edge.

Across a month: 20 volatile sessions × 40 pip loss per session = 800 pips. If you're trading micro contracts, that's nothing. If you're trading 10-lot, that's $400-$800/month in slippage from throttling alone.

But slippage is just the visible cost. The hidden cost is worse:

• Rejection cascades: Your first order gets throttled and rejected. Your second order (the hedge) also gets rejected. Now you're exposed. The position gaps against you 100 pips before you can re-enter.
• Forced liquidations: During a flash crash, your orders queue up. By the time they execute, you're in forced liquidation territory. The broker closes your position at market price and charges you the liquidation fee.
• Missed arbitrage windows: Crypto spreads collapse during volatility. Your bot tries to capture the 5-pip spread across two exchanges. Rate limits delay execution by 100ms. The spread closes. You're stuck with half the position.
• Account kills: If your strategy depends on consistent execution timing, rate limit delays break the entire strategy. Traders blame the bot. The bot is fine. The infrastructure is broken.

How Professionals Escape Rate Limits

Professional traders don't fight brokers. They bypass them.

Enterprise accounts get higher rate limits because they come with volume commitments. A trader who does $50M/month in volume gets 1,000 requests/second. A retail trader gets 50. That's not a bug. That's a feature.

But professional traders go deeper. They:

1. Use prime brokers with STP/ECN routing. Straight-through processing means your order hits the exchange directly, not the broker's queue. No throttling.
2. Implement request batching. Instead of sending 100 individual orders per second, professionals batch 10 orders into 1 API call. Same result, 1/10th the API calls.
3. Use multiple accounts. Professional traders split volume across 3-5 accounts under different brokers. Each account gets its own rate limit. Combined: 5 accounts × 1,000 requests = 5,000 requests/second.
4. Throttle at the application layer. Professional bots don't send every order immediately. They queue orders internally and release them at the broker's rate limit ceiling.
5. Use order aggregation. Instead of sending 10 separate stop-loss orders, professionals send 1 order that manages 10 positions. Broker sees 1 API call. Reality: 10 hedge positions.

The common thread: professionals work with broker infrastructure, not against it. Retail traders hit the limits and blame the bot.

The Throttling Arms Race

As retail automation becomes common, brokers are lowering retail rate limits.

In 2018, retail accounts got 500 requests/second. In 2023, that dropped to 100. By 2026, expect 20-50 for most retail accounts. Brokers want retail traders to slow down. They don't want fast bots cannibalizing the spread.

Worse, brokers actively detect high-frequency behavior. If your bot sends 100+ requests per second for more than a few minutes, the broker flags your account, locks it for 24 hours, or terminates the relationship.

This is a gray area. Brokers claim it's necessary. Retail traders claim it's unfair. The truth: brokers don't want retail traders winning consistently. If your bot is good enough to outrun their infrastructure, you're a liability.

What Retail Traders Can Do Right Now

If you're trading manually, rate limits don't affect you. If you're using a bot, you have three paths:

Path 1: Accept the throttling. Trade low-frequency strategies. 1-5 trades per day. Rate limits never matter. This works if your edge is in strategy, not speed.

Path 2: Switch to an STP/ECN broker. Interactive Brokers, Saxo Bank, and FXCM offer true ECN routing with no internal throttling. Your rate limit is set by the exchange, not the broker. You'll pay 2-3x more in commissions, but you won't get throttled.

Path 3: Use a professional bot architect. A custom EA built for your broker and your strategy can work with rate limits instead of against them. It queues orders intelligently, batches requests, and times execution for optimal fill probability. Most retail bots are generic templates. Custom bots are built to win on your specific broker.

Most retail traders pick Path 1. Professional traders pick Path 2 or 3.

The Bottom Line: Your Broker Doesn't Want Your Bot To Win

Rate limiting isn't a technical necessity. It's a business decision. Brokers throttle retail bots because fast, winning bots are bad for broker economics.

If you're building a bot that sends 100+ orders per day, rate limits are your ceiling. You can fight them. You can work around them. Or you can hire a team that's already solved this problem 660 times.

Alorny builds custom EAs that execute within broker rate limits. We don't fight infrastructure. We architect around it. Your bot gets routed intelligently, uses request batching, and times orders for maximum fill probability. Result: consistent execution even during volatile sessions when retail bots get throttled.

We've built over 660 EAs on MQL5. We know every broker's quirks, every throttling strategy, every workaround. Your bot works because it's built for your broker, not for hypothetical traders.

See How We'd Build Your Bot

Tell us your strategy and your broker. We'll show you in 45 minutes how a custom EA handles your exact edge without hitting rate limits. Then we'll build it in a few hours. Your bot starts from $300 and executes clean where retail bots choke.