List All Configured Accounts
November 17, 2025 (November 16, 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.
{ "jane.doe@gmail.com": { "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" } }, "john.smith@gmail.com": { "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": "useapi.net ⁝ Unauthorized", "code": 401 }
Model
An object keyed by account email, each with the account’s health, backend, project and next automatic refresh.
The accounts, keyed by email, field by field
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. Every request for it answers596: add it again with the automated setupnextRefresh- When the next automatic refresh runs, every 2 to 3 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", otherwise the reason the account does not work and what to do
backend: 'flow' | 'labs' // flow: the account signs in with its `flow.google.com` cookies. labs: an account added
// before 2026-09-12 that stopped working on 2026-10-21, add it again
error?: string // the error that stopped the account, the same text as health
created?: string // ISO 8601 timestamp, first add
updated?: string // ISO 8601 timestamp, most recent add, absent on an account last added before 2026-09-16
sessionData?: { // left from the old Google Labs sign-in on an account first added before 2026-10-21, no longer used
expires: string // ISO 8601 timestamp, when that old sign-in expired
}
project?: { // the account's Google Flow project, where generations go
projectId: string // Google Flow project id
projectTitle: string // project title, set when the project was created
}
nextRefresh?: { // the next automatic session refresh, absent once a refresh stopped on an error
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);