Google Flow

November 17, 2025 (September 30, 2026)

Table of contents

  1. Automated setup (recommended)
  2. Use a dedicated Gmail account
  3. If Google asks for a phone number
  4. Manual setup
    1. Start the browser without device-bound sessions
    2. Sign in to Google Flow
    3. Copy the https://accounts.google.com cookies
  5. Verify and add account
  6. Configure Captcha Providers

Approximately 5 minutes to complete setup steps.


This is the setup guide for Google Flow API. An active Google account and a useapi.net subscription are required for the API to work.

Use our guided browser setup to configure your account automatically — no DevTools or cookie copying needed. Enter your API token, log in with Google in the remote browser, and your account is ready.

Open automated setup

Prefer manual setup? Continue with the steps below.


Google Flow creates cinematic AI clips with Veo, images with Nano Banana 2 Lite, Nano Banana 2 and Nano Banana Pro.

Use a dedicated Gmail account

⚠️ Use a dedicated Gmail account for this API — do NOT use your personal Gmail account.

When creating a new account:

  1. Enable 2-Step Verification with Microsoft Authenticator, and save the backup codes. Avoid Google Authenticator — it backs its codes up to the Google account it is signed into, which would link this dedicated account to your personal one.
  2. Keep your sign-ins consistent. If you use a VPN, pick one region and stay with it rather than switching locations — an account that appears from different places in a short time is what Google treats as suspicious. The automated setup above signs in from a US browser, so it needs no VPN on your side.

If Google asks for a phone number

Occasionally Google shows a “Verify it’s you” page and asks for a phone number to text a code to, even on an account that never had one. Any number that can receive SMS works. It does not have to be one already on the account.

If you’d rather not use your personal number, get an inexpensive prepaid line just for this — for example a Tello eSIM on its cheapest plan with texts (about $5/month, activated online). Install it on any phone, receive the code there, and keep the line active so you can pass future checks.

Avoid online SMS-rental and “free virtual number” services. Google rejects most of them, and a rejected number can make the lock harder to clear.

Manual setup

⚠️ Do NOT use Google Chrome. Google’s integration with Chrome interferes with cookie extraction. Use Brave or Ungoogled Chromium instead.

You sign in to Google Flow, then copy the https://accounts.google.com cookies from Developer Tools and paste them into the cookies field below.

Start the browser without device-bound sessions

Chromium browsers on Windows and Mac now bind a Google sign-in to the device (Google’s Device Bound Session Credentials). Cookies copied from a bound session are refused anywhere else, so the account cannot be added or stops working. The browser’s own flags page does not turn this off (Google overrides it), but a command-line switch does. The automated setup is not affected.

  1. Quit Brave completely, including any instance left in the system tray (check Task Manager for brave.exe, on a Mac use Cmd+Q). A running Brave ignores the switch.
  2. Start it from the Run box (Win+R) with this command, which opens a private window with no cookies and without device-bound sessions:
"C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe" --incognito --disable-features=EnableBoundSessionCredentials,DeviceBoundSessions

On a Mac, run the same switches from Terminal:

open -na "Brave Browser" --args --incognito --disable-features=EnableBoundSessionCredentials,DeviceBoundSessions

Ungoogled Chromium takes the same --disable-features switch. Keep this window open for the steps below.

Sign in to Google Flow

Navigate to https://flow.google.com and click Create with Google Flow 1.

Sign in with your dedicated Gmail account 1.

Enter your password, then the 2-Step Verification code 1. Google names Google Authenticator here whichever authenticator app holds the code.

⚠️ You MUST check Don't ask again on this device 2 — skipping it will break the API session.

Once signed in you see Google Flow. Click New project 1 to open a project, and keep it open for the next step.

Copy the https://accounts.google.com cookies

  1. Open Developer Tools: right-click anywhere on the page and select Inspect (or press F12), then open the Application tab 1
  2. Under Cookies, select https://accounts.google.com 2
  3. Click in the cookie table and select all cookies (Ctrl+A) 3
  4. Copy them (Ctrl+C, or right-click and Copy) 4, and paste them into the cookies field below

Before you paste, look for __Secure-1PSIDRTS in what you copied. If it is there, the session is device-bound and will be refused: close every Brave window and start again with the command above.

Verify and add account

Use the form below to verify your cookies and add your Google Flow account.

Select Add Account to complete setup, or Verify to test your cookies first. You should receive response 200 if successful. You can also use POST /accounts directly.

⚠️ Right after adding the account, close the private Brave window. Do NOT sign out of Google first — signing out ends the session the API now uses.

⚠️ The API now manages this Google account session.

Do NOT access this Google account via AI Studio or Google Flow directly (browser or any other means). Using the same account through both the API and direct access will break the session and require you to redo this entire setup.

Configure Captcha Providers

Image and video generation requires reCAPTCHA v3 Enterprise solving.

Users receive 300 free captcha credits when adding their first Google Flow account. These credits are used automatically, so you can start generating images and videos right away without configuring any provider. Check your remaining credits via GET /accounts/captcha-providers.

After free credits are exhausted, you must configure at least one provider’s API key before using POST /images, POST /images/upscale, or POST /videos.

Supported Providers:

Provider Cost per 1K Avg Solve Time Reports Back Website
AntiCaptcha ~$2.00 ~8-12s Yes anti-captcha.com
CapSolver ~$3.00 ~8-12s Yes capsolver.com — use promo code useapi for 8% discount
EzCaptcha ~$2.50 ~2-5s No ez-captcha.com
YesCaptcha varies ~8-12s No yescaptcha.com
CapMonster ~$1.50 ~10-30s Incorrect only capmonster.cloud
SolveCaptcha ~$0.80 ~30-60s ⚠️ Yes solvecaptcha.com
2Captcha ~$2.99 ~30-60s ⚠️ Yes 2captcha.com

⚠️ SolveCaptcha and 2Captcha typically take 30-60 seconds per solve versus ~2-12 seconds for the others. They work well as low-cost fallbacks but can increase request latency as primary providers.

EzCaptcha solves in real time, in about 2–5 seconds, so a token Google rejects costs little time before the next provider takes over.

Reports Back — providers that support solve-result reporting receive correct/incorrect feedback after each use, which improves token quality over time.

If you have two or more captcha providers, most requests start with the one Google is accepting best right now, and moves to the next one if the captcha is rejected. captchaOrder only picks which providers to use and how many tries to make, not the order. We recommend adding at least two providers, for example AntiCaptcha and CapSolver, and ideally EzCaptcha too, so fewer captchas are rejected and you pay for fewer of them. How it works: Provider order.

Setup Steps:

  1. Create an account with one or more providers above
  2. Purchase credits and obtain your API key from the provider’s dashboard
  3. Configure your API key(s) using POST /accounts/captcha-providers

Tips:

  • Configure more than one provider. The API tries the best of them first and falls back to the next on a rejection, as described in Provider order.
  • GET /accounts/captcha-stats shows how each provider is doing right now and which one the API currently puts first.
  • Each image/video generation attempt requires one captcha solve (~$0.80-$3.00 per 1,000 generations)

Start using the API

A single $15/month subscription covers every API on useapi.net — one token, all services. You connect up to 3 of your own provider accounts per service, and useapi.net handles the REST API, load balancing, and polling.

Subscribe — $15/month

Pricing, crypto payment, and volume options — full refund within the first 14 days if you have fewer than 50 successful generations.