List All Configured Accounts

November 17, 2025 (September 16, 2026)

Table of contents

  1. Request Headers
  2. Responses
  3. Model
  4. Examples
  5. Add your accounts again before they stop working
    1. What already fails on a labs account
    2. Why this is happening
    3. Try It

List all configured Google Flow accounts.

To get a specific account use GET /accounts/email.

https://api.useapi.net/v1/google-flow/accounts

Request Headers 

Authorization: Bearer {API token}

Responses

  • 200 OK

    Returns a map of all configured accounts, keyed by email address.

    {
  "a***@gmail.com": {
    "created": "2025-11-09T22:02:04.802Z",
    "updated": "2026-09-16T18:18:59.337Z",
    "backend": "flow",
    "health": "OK",
    "nextRefresh": {
      "scheduledFor": "2025-12-01T11:46:01.000Z"
    },
    "project": {
      "projectId": "a7e08e13-a6ea-4945-9841-cb4147e4f024",
      "projectTitle": "Nov 11 - 02:56"
    },
    "sessionData": {
      "expires": "2025-12-01T12:46:01.000Z"
    }
  },
  "b***@gmail.com": {
    "created": "2025-11-10T02:56:58.864Z",
    "backend": "labs",
    "health": "OK",
    "nextRefresh": {
      "scheduledFor": "2025-12-01T09:13:16.000Z"
    },
    "project": {
      "projectId": "47050a10-06f4-4469-8ab0-6d294c703508",
      "projectTitle": "Nov 11 - 02:56"
    },
    "sessionData": {
      "expires": "2025-12-01T10:13:16.000Z"
    }
  }
}

    If no accounts are configured, returns an empty object {}.

  • 401 Unauthorized

    Invalid API token.

    {
  "error": "Unauthorized"
}

Model 

// Map of email to account summary
{
  [email: string]: {
    health: string               // "OK" | "<error>"
    backend: 'flow' | 'labs'     // 'labs' accounts need adding again — see the note below
    error?: string               // Error message if health check failed
    created?: string             // ISO 8601 timestamp, first add
    updated?: string             // ISO 8601 timestamp, most recent add
    sessionData?: {
      expires: string            // ISO 8601 timestamp
    }
    project?: {
      projectId: string
      projectTitle: string
    }
    nextRefresh?: {
      scheduledFor: string       // ISO 8601 timestamp
    }
  }
}

Examples 

  • curl -H "Authorization: Bearer YOUR_API_TOKEN" \
     "https://api.useapi.net/v1/google-flow/accounts"

  • import requests

token = 'YOUR_API_TOKEN'
headers = {'Authorization': f'Bearer {token}'}

response = requests.get('https://api.useapi.net/v1/google-flow/accounts', headers=headers)
print('All accounts:', response.json())

  • const token = 'YOUR_API_TOKEN';

const response = await fetch('https://api.useapi.net/v1/google-flow/accounts', {
  headers: {
    'Authorization': `Bearer ${token}`
  }
});

const accounts = await response.json();
console.log('Configured accounts:', accounts);

Add your accounts again before they stop working

Google is switching off the backend that Google Flow accounts used to run on. Accounts added before 2026-09-16 are still on it and need to be added again.

Check which ones with GET /accounts and read the backend field on each account:

backend What it means What to do
flow On the current backend Nothing
labs On the old backend Add the account again at Setup Google Flow

Adding an account again takes about a minute with the guided browser setup. Your code does not change — same endpoints, same parameters, same responses — and the account keeps its project, characters, voices, credits and original created date.

What already fails on a labs account

These four return 404 with the message Flow RPCs have been deprecated and disabled:

Generating images and videos still works on a labs account. That is the part to plan around — Google is retiring the whole old backend, not these four endpoints, so generation stops too once the remaining endpoints are switched off. Google has not published a date, which is the reason to move now rather than wait for one.

Why this is happening

Google moved Flow to flow.google.com on 2026-09-10 and replaced the old authorization with a cookie-based one. On 2026-09-15 it started disabling the old endpoints. Adding an account again captures what the new backend needs.

Try It