List All Configured Accounts
November 17, 2025 (October 23, 2026)
Table of contents
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}
API tokenis required, see Setup useapi.net for details.
Responses
-
Returns a map of all configured accounts, keyed by email address.
{ "[email protected]": { "health": "OK", "backend": "flow", "created": "2025-11-09T22:02:04.802Z", "updated": "2026-10-22T16:04:11.512Z", "project": { "projectId": "a7e08e13-a6ea-4945-9841-cb4147e4f024", "projectTitle": "Nov 11 - 02:56" }, "nextRefresh": { "scheduledFor": "2026-10-23T16:11:37.000Z" } }, "[email protected]": { "health": "Google shut down the old Google Labs sign-in on 2026-10-21. This account was added without the APISID and SAPISID cookies that the Google Flow sign-in needs, so it no longer works and cannot be refreshed. Add it again with the automated setup at https://useapi.net/assets/setup-browser/google-flow, which captures every cookie needed (guide: https://useapi.net/docs/start-here/setup-google-flow).", "backend": "labs", "created": "2025-11-10T02:56:58.864Z", "project": { "projectId": "47050a10-06f4-4469-8ab0-6d294c703508", "projectTitle": "Nov 11 - 02:56" } } }If no accounts are configured, returns an empty object
{}. -
Invalid API token.
{ "error": "Unauthorized" }
Model
health-OKwhen the account is ready, otherwise the reason it is not and what to dobackend-flowwhen the account runs on the flow.google.com cookies.labsmarks an account added before 2026-09-12 without theAPISIDandSAPISIDcookies, which stopped working on 2026-10-21 and must be added again, see belownextRefresh- When the next automatic refresh runs, about every 2 days
An account first added before 2026-10-21 can also show sessionData left from the old Google Labs sign-in. The API no longer uses it.
// Map of email to account summary
{
[email: string]: {
health: string // "OK" | "<error>"
backend: 'flow' | 'labs' // 'labs' accounts must be added again — see below
error?: string // Error message if health check failed
created?: string // ISO 8601 timestamp, first add
updated?: string // ISO 8601 timestamp, most recent add
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);
Accounts that must be added again
Google switched off the old Google Labs sign-in on 2026-10-21. Google Flow accounts now run only on the flow.google.com cookies, and an account added without them no longer works.
Check your accounts with GET /accounts and read the backend field on each one:
backend | What it means | What to do |
|---|---|---|
flow | Runs on flow.google.com | Nothing |
labs | Added before 2026-09-12 without the APISID and SAPISID cookies, stopped working on 2026-10-21 | Add the account again with the automated setup |
Every request for a labs account answers 596, and its health carries the same message:
{
"error": "Google Flow account [email protected]: Google shut down the old Google Labs sign-in on 2026-10-21. This account was added without the APISID and SAPISID cookies that the Google Flow sign-in needs, so it no longer works and cannot be refreshed. Add it again with the automated setup at https://useapi.net/assets/setup-browser/google-flow, which captures every cookie needed (guide: https://useapi.net/docs/start-here/setup-google-flow)."
}
Adding an account again takes about a minute with the automated setup, which signs in to Google in a browser and captures every cookie needed (see Setup Google Flow). Your code does not change — same endpoints, same parameters, same responses — and the account keeps its project, characters, voices, credits and original created date. A project you deleted in Google Flow is replaced by a new, empty one.
Why this is happening
Google moved Flow to flow.google.com on 2026-09-10 and began disabling the old Google Labs endpoints on 2026-09-15. On 2026-10-21 it switched off the Google Labs sign-in itself, so an account can now sign in to Google Flow only with its Google account cookies, APISID and SAPISID included.