Receive a Verification Code Online With Gmail

Q: How do I receive the code programmatically instead of watching a page?

Poll GET /v1/orders/{orderId} every few seconds after creating the order; the response includes an otp array once a code has arrived. Full examples are in the API docs.

Updated October 13, 2026 · 5 min read

Most ways of getting a verification code assume you already have an inbox to check. This one flips that around: you rent the inbox for the occasion, and the code shows up on a web page instead of in a mailbox you have to sign in to. That is the idea behind receiving a verification code online through OTPGmail.

What "receiving it online" means here

Normally, getting a code by email means opening your mail app, finding the message, and copying the code out of it — an extra step, and one more place your address needs to be handed to. Receiving it online instead means:

You rent a real @gmail.com or @icloud.com address for the service you are signing up for.
That service sends its code to the rented address as it normally would.
Instead of opening a mailbox, you read the code directly on your OTPGmail order page, updated automatically as soon as it lands.

There is no mailbox login anywhere in that sequence. You get the code, not the inbox.

The four-step flow

Rent the inbox. On the rent page, pick the service and the inbox type, @gmail.com or @icloud.com. You are charged only once an address is issued.
Hand the address to the service you're registering with, exactly as you would your own email, and ask it to send the code.
Watch the order page. It updates on its own the moment the code arrives — no refresh button required, though one is there if you want it.
Use the code, then stop watching. If the service sends more codes — a login confirmation, a device check — the same page shows them too: extra codes cost nothing within the order period when the service sends more than one, and the limit and time window are shown before you rent.

If nothing arrives within 25 minutes of renting, the order cancels itself and refunds you in full automatically, so checking the page for those 25 minutes costs nothing if the code never comes.

Why the order page instead of a mailbox

Reading the code on a web page rather than in a mailbox removes a few steps that normally slow this down: no switching apps, no searching a folder for the right message, and no risk of a stray filter hiding it somewhere you won't think to check. It also means the same interface works whether you rented @gmail.com or @icloud.com — the order page looks and behaves identically either way, so switching inbox type for a later order doesn't change how you receive the code.

Doing it from a script instead of a browser

The order page is really just a friendly view of the same thing the API returns, so anything you can do by watching a page, you can do by polling an endpoint:

POST /v1/orders with a service code, and an optional inbox domain, creates the order and returns its ID.
GET /v1/orders/{orderId} polled every few seconds returns the order's status, and an otp array holding the code once one has arrived.
POST /v1/orders/{orderId}/cancel cancels an order early, with the same refund you would get from letting the 25 minutes run out.

This is how QA suites and onboarding scripts receive a verification code online without a person watching anything — see Gmail for OTP for the bigger picture and the API docs for the full reference, including error codes for out-of-stock inboxes and rate limits.

What you can and can't do with the code once you have it

The code is yours to use the moment it appears — paste it into whatever form is waiting for it, same as you would from any inbox. What you cannot do is anything that requires the mailbox itself: there is no sending mail from the rented address and no browsing older messages. A rented inbox only receives codes within its order window, which the rent page shows before you pay; it is not a long-term mailbox — if you expect to need a code the next day, place a fresh order closer to when you will actually use it rather than renting far in advance. If a task genuinely needs an active, logged-in Gmail session rather than one code, that calls for a different product: OTPGmail also sells short-lived Gmail accounts you can sign in to — see buy short-lived Gmail accounts, and rent vs buy for the difference.

Whatever the code unlocks on the other end, follow that service's own terms about accounts and verification; OTPGmail is not responsible for how a received code gets used afterward.

Frequently asked questions

Do I need a Gmail password to receive the code online?

No. You never receive or need a password — the code appears directly on your OTPGmail order page.

Can I receive more than one code at the same address?

Yes, if the service sends more than one: extra codes cost nothing within the order period, and the limit and time window are shown before you rent. Many services send just one code per inbox, so do any step that needs another code right after sign-up, while the order is still open.

How do I receive the code programmatically instead of watching a page?

Poll GET /v1/orders/{orderId} every few seconds after creating the order; the response includes an otp array once a code has arrived. Full examples are in the API docs.

Can I receive the code on my phone instead of a computer?

Yes. The order page is a normal web page, so it works in any mobile browser. Nothing about receiving the code requires a desktop, except where a specific target service's own sign-up form has that requirement.

What if the code never shows up online?

Wait out the 25-minute window for an automatic refund, or work through the 7-point checklist to understand why before trying again.

Rent an inbox and watch for your code, or read the API docs to automate the whole flow.