Bulk Gmail Rental for Teams: Up to 200 Inboxes

Updated October 2, 2026 · 5 min read

Renting one Gmail inbox at a time works fine for a single sign-up. It gets tedious fast if you need thirty, fifty or a hundred addresses for the same reason — a QA run, an agency onboarding several clients, or a batch of test accounts. Bulk rental exists for exactly that: one purchase, many inboxes, delivered together.

What bulk rental is

A bulk order issues 1 to 200 inboxes in a single batch, all for the same service, at the same unit price as a single rental, held for 24 hours. Gmail batches give each inbox its own code link for scripts, with a .txt export you can drop straight into a script or spreadsheet; iCloud batches are read on the batch page or through the API. Gmail or iCloud rental explains how to choose between the two inbox types.

The 24-hour hold gives you a full day to work through the batch rather than a race against the clock — plenty of time to run a QA suite overnight or divide addresses among a team the next morning, without needing to use every address the moment it is issued.

Who actually needs it

Bulk rental earns its keep once single orders start feeling like the wrong tool:

QA and developer teams running the same sign-up flow across many test accounts in one session, where placing dozens of individual orders would just slow the run down.
Agencies opening accounts for several clients at once, where a batch with an export file is easier to divide up than dozens of separate receipts.
Anyone testing at scale — load-testing a registration flow, or comparing delivery behavior across a large sample — who needs many real addresses on hand immediately rather than issued one at a time.
Agencies and freelancers billing by the account. A single export file with a clear quantity and price per batch is easier to attach to an invoice than dozens of separate single-order receipts.

If you only need a handful of addresses, or you want a refund on every single one that fails to receive a code, single orders through the rent page or the API usually serve you better than a batch — see the trade-off below.

How it works

Open the bulk rental page and pick the service, the inbox type (Gmail or iCloud) and the quantity, up to 200 inboxes.
Pay for the batch; your balance is charged for the full quantity at once, at the same per-inbox price as a single rental of that service.
Receive the addresses on the batch page — Gmail batches also come as a .txt export with a code link per inbox — ready to paste into whatever is doing the sign-ups: a script, a spreadsheet, or a manual queue.
Use each address within the 24-hour hold. Codes show up through each inbox's code link for Gmail batches, and on the batch page or through the API for iCloud batches, just without an individual order page for each one — you track delivery through the batch and your own process.

The trade-off: no per-inbox refund

This is the one rule that separates bulk from single rental, and it is worth internalizing before you buy a batch: inboxes in a batch that never receive a code are not refunded. A single order refunds automatically after 25 minutes with no code; a bulk order does not carry that same guarantee address by address. Only a shortfall, or a batch that cannot be bought, is refunded. The terms and refund guide covers this alongside every other rule for rented inboxes.

In practice this means bulk rental suits a job where you expect most addresses to succeed and can tolerate a few misses — typical for well-behaved sign-up flows — rather than a service known for stopping registrations early, where the individual refund from single orders would serve you better financially.

Bulk rental vs the API for volume

Both handle volume, but differently:

	Bulk rental	API, one order at a time
Inbox type	Gmail or iCloud	Gmail or iCloud
Refund on no code	Not refunded per inbox	Refunded automatically after 25 minutes
Delivery	The whole batch up front (Gmail: .txt export with code links)	Up to 200 inboxes per API call, as needed
Best for	A known batch size, used within 24 hours	Ongoing or unpredictable volume, or when you want a refund on every failure

Teams that need both the guarantee and real volume often use the API in a loop instead of a single bulk order, accepting the extra calls in exchange for a refund on anything that fails. See the Gmail OTP API for how that loop is built. Batches themselves are bought on the web only; the API can list your batches and read their codes (GET /v1/batches), but not create them.

Frequently asked questions

What is the maximum size of a bulk order?

200 inboxes per batch (the minimum is 1), all for the same service and the same inbox type, Gmail or iCloud.

Do bulk inboxes get refunded if they don't receive a code?

No. That is the main difference from single orders, which refund automatically after 25 minutes with no code. Only a shortfall, or a batch that cannot be bought, is refunded. Budget bulk purchases accordingly.

Can I get iCloud addresses in bulk?

Yes. iCloud batches work like Gmail batches, at the same unit price as a single rental and held for 24 hours; their codes are read on the batch page or through the API, while Gmail batches give each inbox its own code link for scripts.

Is the API a better option than bulk rental for large volume?

It depends on your priorities. The API refunds each failed order individually, but you create the orders yourself (up to 200 inboxes per call); bulk rental delivers everything at once but without a per-inbox refund. Many teams use both depending on the job.

Can I mix services in a single bulk order?

No, a batch is issued for one service at a time. For several services, place a separate batch for each, or use single orders through the API if you need a small, mixed set.

Start a batch on the bulk rental page, or automate one address at a time with the API docs.