Desktop Chrome only

Now on Google Play

Start free trial

SnipeBid needs Chrome on a computer or an Android phone.

Send the link to my computer
What works on your iPhone

Control & safety

Safety & limits

SnipeBid is built to behave carefully. Here is exactly how it paces itself, and what you can control.

One request at a time

Every request SnipeBid sends to EA (searches, buys, bids, listings, watchlist checks) goes through one queue. Requests are sent one at a time, spaced like a person, capped per minute, and frozen completely during a cooldown. Delays are random inside a range, and now and then one is stretched further, like a person getting distracted.

Paces

Pick a pace in Settings → Safety. The default is Normal.

TimingSafeNormalAggressive
Pause before the next search7–14 s4.5–9 s3–6 s
“Reading the results” before a bid (and a Human buy)1.4–2.8 s0.95–1.9 s0.65–1.3 s
Minimum gap between any two requests1.8–3.4 s1.2–2.4 s0.85–1.7 s
Minimum gap between two bids4–8 s2.8–5.5 s2–3.8 s
Max requests per minute101522
Short breakevery 5–9 min, for 45–150 severy 10–15 min, for 20–60 severy 9–15 min, for 20–70 s
Long breakevery 35–55 min, for 8–16 minevery 55–80 min, for 5–10 minevery 60–90 min, for 4–8 min

The Buy Now reaction (Human, Fast, Turbo) is set separately; see Sniper.

Warm-up

SnipeBid always uses the Safe timings for a while, whatever pace you picked:

  • the first 3 minutes after you press Start,
  • 2 minutes after a long break,
  • 4 minutes after an EA cooldown ends,
  • 3 minutes after reconnecting to an expired session.

Breaks

Short and long breaks come at irregular times (see the table). During a break the panel shows a countdown ring; press Skip to end it early.

Search limits per hour and per day

SettingDefaultWhen it’s reached
Max searches / hour600SnipeBid pauses (Hourly limit) and resumes as soon as the oldest search of the last hour ages out.
Max searches / day2,500The bot stops with daily search limit reached. The count resets at your local midnight.

Both limits count every browser and computer running SnipeBid on the same EA account: each browser reports its searches to your SnipeBid account every 30 seconds and gets the totals back. If the searches were made in another browser, the hourly pause waits 5 minutes and checks again.

Start again after the daily reset (Settings, on by default): when the daily cap stops the bot, it starts again by itself at a random time 3 to 20 minutes after your local midnight, in the same mode (snipe, bid or both), with the new day’s count at 0. Until then the status reads Daily search limit reached · starts again at 00:14, in the panel and in the phone remote. It survives a page reload; if the web app tab is closed at that time, it starts once you open it again that day. It only starts once, even with several tabs open, and it waits for the EA session if that is gone. While it waits, the Start button reads Daily search limit reached · resumes at 00:14 (with your time); tap it and choose Cancel auto-start if you don’t want it to start. A stricter pause always wins: after a safety stop, 3 EA blocks in a day or an EA verification check it doesn’t start, and a running EA cooldown is waited out first. Turn the setting off to stay stopped until you press Start.

Daily search limit counts (Settings, Advanced): Per calendar day (resets at midnight) is the default. With Per 24 hours from the first search the count starts with the first search and runs for 24 hours: midnight doesn’t touch it, so searches left over in the evening are used through the night. When the cap is used up the bot stops; 24 hours after that first search the count is back to 0 and the next search starts a new 24 hours. Start again after the daily reset then starts the bot 3 to 20 minutes after those 24 hours end instead of after midnight, and the panel shows when the count resets (e.g. 1,840/2,500 · resets 02:14). The hourly limit and the pause after 3 EA blocks (until midnight) stay as they are, and your stats still count per calendar day.

Spend limits

SettingDefaultWhat it does
Session spend limit0 (no limit)Stops the bot (spend limit reached) before a buy would take this run’s spending over the limit.
Keep at least0Never buys or bids below this coin balance.
Max coins in bids (%)100How much of your coins may be tied up in bids. See Bidder.
Daily loss guard3%When today’s flips lose more than this share of your bankroll (at least 500 coins), Scout Autopilot adds no new cards until midnight. Trading continues. 0 = off, up to 20%.

When EA pushes back: cooldowns

When EA answers with a rate limit or a temporary market lock, SnipeBid stops sending anything until a cooldown ends. The panel shows 🛡️ EA cooldown with a countdown.

EA’s answer1st time2nd3rd and later
Too many requests / rate limited (HTTP 426, 429)3 min10 min30 min
Market temporarily locked, “soft ban” (HTTP 512, 521)Cooldown setting (15 min)× 2 (30 min)× 4 (60 min)

The repeat count resets after an hour without any push-back. Cooldown after a block in Settings → Safety sets the base time for market locks. After a cooldown SnipeBid eases back in at the Safe pace.

If you press Start during a cooldown or safety pause, SnipeBid asks first: Continue pause starts by itself when the pause ends; Start anyway (skip pause) starts now and makes a longer EA ban more likely. The pause stays in place after a reload and on your other PCs, and Settings → Safety shows A pause is active: … left.

The first 10 minutes are locked. When an EA cooldown begins after a market lock or rate limit (HTTP 512, 521, 426, 429), Start and Start anyway are locked for the first 10 minutes and show a countdown. This holds in the panel, on the phone remote and in the Android app, because starting into a fresh ban makes it longer. After those 10 minutes Start anyway works as described above.

Every wait names its reason. Whenever SnipeBid pauses and will start again by itself, the Start button, the status pill at the top, the phone remote and the Android notification say why in plain words: Daily search limit reached · resumes at 00:14, EA cooldown · resumes at 22:10, Safety pause · resumes at 22:10 (or Safety stop), Prices out of date, Can’t check prices or Waiting for an EA fix. The pill says the same as Paused — daily search limit (2,500), with an ⓘ next to it for the daily limit: what the limit protects and where to change it (Settings › Safety › Max searches / day). While the bot is running, a short pause names its reason in the pill too, for example hourly search limit · 4:12 or fewer deals now · back in 1:20:00, and a stop from a phone schedule reads stopped by your phone schedule · starts tomorrow 18:00. Tap the button during a wait and the question repeats the reason: Keep waiting leaves it as it is, Cancel auto-start turns it into a normal Start button.

Three blocks in two hours: stopped for today

If EA rate-limits or locks the market 3 times within 2 hours, SnipeBid doesn’t keep coming back for more. It stops with EA blocked the market 3 times in 2 hours — stopped until tomorrow and rests until your local midnight. If you press Start before then, SnipeBid warns you that starting again today makes a longer market ban more likely and only starts if you choose Start anyway.

While SnipeBid is stopped for the day, be it by the daily search limit or by this stop after 3 EA blocks, nothing SnipeBid sends reaches EA until midnight (the same day boundary as the daily limit). That covers everything, not only trading: SBC solving and submitting, FC Hub, Gallery, ⭐ Keep and the panel’s own reads. Whatever needs EA shows Paused for today to protect your account — back at 00:00 (with your time) instead of sending anything. What you do yourself in EA’s web app is never blocked.

Safety pause and safety stop

SnipeBid checks every answer EA sends. The everyday ones are expected: success, “already sold”, “bid too low”, “no coins”, an expired session, rate limits and market locks (those have their own handling above). Anything else is unusual: errors like HTTP 400, 403, 404, 460 or 500, timeouts, network errors, and answers that are missing the data SnipeBid needs (for example a search result without any listings field), which usually means EA changed something.

What happensWhat SnipeBid does
5 unusual answers within 5 minutes, or 3 in a row with the same error on the same kind of requestSafety pause: sends nothing to EA for 10 minutes. The panel shows 🛡️ Safety pause with the reason, for example unusual EA errors (HTTP 460 on search), and a countdown. Afterwards it eases back in at the Safe pace. SnipeBid also checks right away whether we paused that feature.
A second safety pause within an hourSafety stop: the bot stops with Safety stop: EA keeps returning errors (…). SnipeBid stopped to protect your account. Your phone alert for stops fires if you set one up.

The fuse also protects what you start by hand. If it trips while the pack sorter, bulk listing, won-items handling or an SBC batch is running, that job stops at its next card with the same message. Try again once the 10 minutes are over.

Scout Autopilot and safety

Scout Autopilot only manages which cards and filters are on your list. It never changes your pace, reaction, search or spend limits, and it doesn’t add searches: the same searches are just aimed where deals are found.

  • Cooldown freeze: during a cooldown, safety pause, verification or day stop, and for 30 minutes after it, Scout makes no changes. After any EA block it waits two hours before changing anything.
  • Daily loss guard: when today’s flips lose more than your set share of your bankroll (Settings › Safety, 3% by default), Scout adds nothing new until midnight. Trading continues. See Daily loss guard.
  • Buy-time guard: no Buy Now or new bid on a card whose price just spiked, whose price is out of date, or that is a promo card on its release day. Scout doesn’t plan such cards either. See The buy-time guard.
  • Shelter during price drops: while prices are sliding, and around the usual Thursday rewards and Friday promo windows, Scout holds fewer of its cards from 10K up and adds none. A Scout card that falls 12% or more in a day pauses for about 3 hours.
  • At most 6 list changes a day, each one shown with its reason and an Undo.

Verification (captcha)

If EA asks for a verification check (HTTP 458), SnipeBid stops; it never tries to solve it. Open Transfers in the web app, run one search by hand, solve the check, then press Start again.

Session expired

If EA says the session expired, SnipeBid pauses and checks again after about 20 seconds, 1 minute and then every 2 minutes. It resumes at a gentle pace once the session works. After 10 minutes without a session it stops and asks you to reload the web app, log in and press Start.

Features paused for an EA change

If EA changes something that makes a feature misbehave, we can pause that one feature for every SnipeBid user within minutes, until an update fixes it. You see a banner in the panel, such as Paused while we fix an EA change: sniper. Back soon., and a running bot stops at its next step (in Both mode, the half that isn’t paused keeps going). It turns back on by itself.

This is a simple on/off switch per feature, checked every 10 minutes, and every 2 minutes while the bot runs. It never runs code from our server, and if our server can’t be reached, everything stays on. See Troubleshooting.

Paused automatically

A feature can also be paused without waiting for us. When several SnipeBid users get the same unusual EA error within a few minutes, our server pauses the features that use those requests for everyone. The banner says what was seen (the server sends it in English): Paused automatically: EA's servers are returning errors., Paused automatically: EA is not answering for several users., Paused automatically: unusual EA errors from several users., or, when we also saw EA change something, Paused automatically: unusual EA errors while we check an EA change. Each one ends with a short note on when it comes back. We are alerted at the same moment.

When no EA change is involved, the pause ends by itself once SnipeBid sees that searches work again (about ten clean minutes with real searches). While it holds, a few bots that the pause stopped run one test search about every 15 seconds (no buys, no bids), so this check never waits for someone to press Start; if yours is one of them, the Activity log says so. When EA actually changed something, it stays paused until we have checked the new EA version and switched the feature back on.

There is nothing to do on your side: no reinstall, no settings change. A sniper or bidder that was running stops when its feature is paused and starts again on its own, in the same mode, if the feature is back within 3 hours; after that, press Start. A problem with only your own connection (your internet is down, or errors on several parts of EA at once) pauses nobody else: your own bot stops itself with a safety pause, as described above, and goes on once your connection is back.

When EA updates the web app

Some features (the SBC solver, the pack sorter, prices on cards) work through parts of EA’s web app. When the web app loads, SnipeBid checks that those parts are still there. If one is missing, only the feature that needs it pauses on your computer, with EA changed the web app; the pack sorter is paused until SnipeBid is updated. in the Log. Our server also notices when a new version of EA’s web app appears; if it changed the parts SnipeBid relies on, the sniper, the bidder and the affected features are paused for everyone until we have checked the new version.

Anonymous error reports

Send anonymous error reports (Settings → Safety, on by default) helps us notice EA changes fast. When SnipeBid hits an error in its own code, or an unusual EA error, it sends:

  • the feature (for example sniper or SBC solver), a short error message and the error code,
  • how often it happened and when, and your SnipeBid version.

Messages are cleaned before they leave your browser: no coin amounts, item or card ids, emails, license keys or EA account names. Normal trading answers such as “already sold” or “outbid” are not reported. Reports are grouped and sent at most every 5 minutes, and right away after a safety pause. Along with them, once per visit, goes the version number of EA’s web app and which of the web app parts SnipeBid uses are present, so we see EA updates as they roll out. Turn the switch off and nothing is sent.

Lower-risk setup

  • Pace Safe or Normal, reaction Human or Fast.
  • Lower Max searches / hour and / day well under the defaults.
  • Set a Session spend limit and Keep at least.
  • Keep the Daily loss guard on and Scout on Safer or Balanced.
  • Keep breaks on (don’t skip them all), and run in shorter sessions.
  • Use a secondary account.
  • New to SnipeBid? The 🛡️ Safe beginner starting setup sets most of this in one click.

For the short overview, see FUT trading bot.

SnipeBid is an independent tool and is not affiliated with, endorsed or sponsored by Electronic Arts Inc. EA SPORTS FC and Ultimate Team are trademarks of Electronic Arts Inc.

Pay with cryptoExtra EA account, paid with crypto

SnipeBid Pro, prepaid. Pick how long you want it:Use the same email as your SnipeBid license, so the extra account is added to it automatically.

Plan

Prepaid, no auto-renew, no free trial · USDT, BTC, ETH, LTC and more · Your key arrives by email after the blockchain confirms

Your privacy choices

We use cookies for analytics & ad measurement (Google, Meta, Microsoft Clarity). You can allow them or opt out at any time. Details