OTP & other settings
Column 3 gathers two groups: OTP Providers (smartphone icon) — where you declare the SMS provider used to receive verification codes, and Other (wrench icon) — API keys and supporting options. Finally, don't forget to click Save Automation to write everything.
OTP Providers — the Flag Verify block
This group now holds a single block: Flag Verify (challenge/iap) — the phone-verification path Google actually still serves. Default provider: smspool, default country id (Indonesia).
The block has three main fields: Provider (dropdown), API Key, and Country (flag + name + dial code). The provider list:
| Provider | Code | Extra sub-fields |
|---|---|---|
| chaycodeso3 | 0 | — |
| viotp | 1 | — |
| dailyotp | 3 | Server ID (3) · Country ID (9) · Service ID (3396) |
| bossotp | 4 | — |
| ironsim | 6 | — |
| codesim | 7 | — |
| smspool | 8 | Country ID |
| hero-sms | 9 | Country ID · Max price per number |
| pvadeals | 10 | Service ID |
| sms222 | 11 | — |
- Pick a provider — In Flag Verify, open the Provider dropdown and choose your SMS service.
- Paste the key — Fill that provider's API Key.
- Choose the country — Set Country for the phone number (default
id— Indonesia). - Sub-fields — If you chose dailyotp fill Server ID / Country ID / Service ID; smspool takes Country ID; hero-sms takes Country ID and a max price per number (leave it empty to let the provider pick); pvadeals takes a Service ID.
- Save — Click
Save Automation.
The Server ID / Country ID / Service ID sub-fields only appear when you pick dailyotp; Country ID on its own also appears for smspool. With any other provider they stay hidden and nothing needs filling in.
Retry Next up to 22 times when Google rejects the phone number — a switch under the provider list, off by default, that applies to every provider. Google uses one message for both ‘this number is limited’ and ‘this account hit its verification limit’, so seeing it does not prove the number is bad — it turns up on brand-new numbers too. When on, the tool presses Next again (waiting each time for the button to come back) and stops the moment the code page appears; only after 22 tries that all stay on the phone page does it move to another number. When off it presses once, as before.
sms222 — numbers you buy in bulk and keep
sms222 works differently from every other provider on the list. You do not rent a number per attempt: you buy a batch once on the provider's own site (a single order can hold up to 50,000 numbers), download their TXT file, and hand those numbers to your accounts. Each number stays alive for 61–100 days, so an account keeps the same phone number for that whole period — which is what you want when the number may be needed again later.
Because of that sms222 needs no API Key, and the Country field auto-fills to US (still editable). What the tool needs instead are two values per account: the OTP Number and the OTP Code Link.
- Buy the numbers — on wawuji.com (the official sms222 shop · Telegram @sms222us), order the quantity you need in one go.
- Download the list — open the order and press
Download TXT. Each line readsnumber|token. - Assign them — in the Accounts tab tick the rows, then Actions → Set OTP Number, and paste the file's contents as they are. No reformatting needed: a tab, a comma or a space work as separators too, and a bare token is accepted instead of the full link.
- Select the provider — in Flag Verify choose sms222, then press
Save Automation.
The assignment screen previews how many pairs will be assigned, skips accounts that are currently running, and — by default — skips accounts that already have a number, so you never overwrite one that is still valid. The code link is stored encrypted, because anyone holding it can read that number's messages.
An account has exactly one number. If Google rejects it, the tool stops that account straight away instead of retrying the same number seven times — give the account a different number and run again.
Other — API keys & options
| Field | What it's for | Note |
|---|---|---|
| ChatGPT API Key | OpenAI key for AI-assisted text generation (content, appeals). | Masked like a password; hint sk-proj-…. Leave blank if you don't use AI. |
| Email Receive (for appeals) | Contact/recipient email used in account appeal & recovery flows. | Not masked; hint your@email.com. |
| Gmail Checker API Key | Key for the check-gmail.live service that checks whether accounts are live/dead. | Masked like a password; the two toggles below depend on it. |
| Fast Check ⚡ | When ON, checks in a faster mode that returns only live/die (skipping deeper checks). | Default OFF; needs the checker key to be useful. |
| Check Flag 🚩 | When ON, also detects accounts with no avatar set (a signal of a fresh/unhealthy account). | Default OFF. |
- AI key — If you use AI features, paste the key into ChatGPT API Key.
- Appeal email — Enter your contact email in Email Receive (for appeals).
- Live/die checking — Paste the
check-gmail.livekey into Gmail Checker API Key, then optionally turn on Fast Check ⚡ (fast, live/die only) and/or Check Flag 🚩 (catch no-avatar accounts). - Save everything — Click
Save Automation.
Save Automation
The Save Automation button in the bottom bar writes the entire page to the database: OTP config, the ChatGPT/email/Gmail keys, the antidetect platform + port + Multilogin credentials, and the whole Run Configuration block (threads, window size, scale, error handling, monitor, proxy toggles).
Nothing on this page persists until you click Save Automation. Leaving the page without saving loses all changes (exceptions: Test Connection and Fetch, which use the on-screen values live). After clicking, wait for the green ✓ Automation config saved! message (auto-hides after 3 seconds). A network error shows ✗ Save failed.