List Project Media

September 1, 2026 (November 16, 2026)

Table of contents

  1. What is listed
  2. Uploads vs generated media
  3. Very large projects
  4. Request Headers
  5. Path Parameters
  6. Query Parameters
  7. Responses
  8. Model
  9. Examples
  10. Try It

List the media held in one project on a Google Flow account. Every entry comes back with a mediaGenerationId you can pass straight to DELETE /assets/email or GET /assets/mediaGenerationId.

This is the endpoint that shows you your uploads. Files you send with POST /assets stay on the Google account after the generation that used them is finished, and nothing removes them on its own — they simply accumulate. likelyUploads counts them, and likelyUpload marks each one.

Find a project id with GET /assets/projects/email, or omit projectId to read the project this account currently writes to.

What is listed

Two collections are merged into one media array: the project’s own timeline, and media attached to the project from elsewhere. The second is where uploads normally sit, and it is usually much the larger of the two — on a real account the project’s own timeline held 8 entries against 292 attached ones, every one of them an upload, some more than nine months old.

Both are listed together because both are stored on the account, both count toward it, and both can be deleted the same way.

Uploads vs generated media

likelyUpload reflects how Google itself recorded the media — as something you uploaded, or as something Flow generated. It is not inferred from the presence of a prompt or any other heuristic.

It is likelyUpload rather than isUpload for one reason: an entry Google records as neither stays false. Those show up as mediaType: "OTHER" and are left out of the likelyUploads count rather than being offered up for deletion on a guess.

Very large projects

One call returns at most 25,000 entries. When a project holds more, the response carries truncated: true. The project’s own timeline comes first, so the attached uploads show up once the timeline holds fewer than 25,000 entries.

There is no cursor. Google sends the whole project on every call, in no particular order, so a later page would cost as much as reading everything. To work through a large project, delete the entries you no longer need with DELETE /assets/email and call again — the next call returns entries the previous one did not. A call that keeps getting back entries you want to keep will keep returning them.

A project of tens of thousands of entries is also slow to read: expect 20 seconds to over a minute per call. The fastest way out is to start the account on a fresh project:

  1. In Google Flow, delete the project whose id is project.projectId in GET /accounts/email.
  2. Add the account again with POST /accounts. The API sees the project is gone and creates a new, empty one for the account.

Everything in the deleted project is gone for good. Characters and voices are kept: they live in a separate project.

https://api.useapi.net/v1/google-flow/assets/media/email?projectId=

Request Headers

Authorization: Bearer {API token}

Path Parameters

  • email is required, URL-encoded. The Google Flow account holding the project.

Query Parameters

  • projectId is optional. Defaults to the project this account currently writes to. Pass a projectId from GET /assets/projects/email to read any other project on the account. It is required when the account has no project on file, in which case the call returns 400 without it.

One call returns up to 25,000 entries. See Very large projects when a project holds more.

Responses

  • 200 OK

    {
      "email": "john@gmail.com",
      "projectId": "3a18acb1-2c6e-478b-bcec-2df19cb8edab",
      "count": 591,
      "likelyUploads": 388,
      "media": [
        {
          "mediaGenerationId": "user:12345-email:6a6f...-image:0115f3c1-...redacted...",
          "mediaType": "IMAGE",
          "createTime": "2026-06-14T00:03:47.401463Z",
          "likelyUpload": true
        },
        {
          "mediaGenerationId": "user:12345-email:6a6f...-video:a1d95d21-...redacted...",
          "mediaType": "VIDEO",
          "createTime": "2026-07-26T21:07:56.856451Z",
          "likelyUpload": false
        }
      ]
    }
    

    An empty project returns 200 with an empty array, not 404.

    {
      "email": "john@gmail.com",
      "projectId": "3a18acb1-2c6e-478b-bcec-2df19cb8edab",
      "count": 0,
      "likelyUploads": 0,
      "media": []
    }
    
  • 400 Bad Request

    No projectId was given and the account has no project on file. Pass one explicitly — GET /assets/projects/email lists every project the account holds media in.

    {
      "error": "Parameter projectId is required (this account has no project on file)",
      "code": 400
    }
    
  • 401 Unauthorized

    Invalid API token.

    {
      "error": "useapi.net ⁝ Unauthorized",
      "code": 401
    }
    
  • 404 Not Found

    The account named in the path is not configured for this token. List what is configured with GET /accounts.

    {
      "error": "Google Flow account john@gmail.com not found",
      "code": 404
    }
    

    Google has no project with this projectId on the account. Google’s own answer is passed through as an error object, which is why this one does not read like the error above. Check the value against GET /assets/projects/email.

    {
      "error": {
        "code": 404,
        "message": "flow.google.com Zzl0ze failed",
        "status": "NOT_FOUND",
        "details": []
      }
    }
    
  • 596 Session Error

    Google rejected the account’s session, and the API is re-verifying the account on its own: retry in about a minute. If Google signed the account out, the account keeps answering 596 and you get a reconnect email: add it again by following Setup Google Flow.

    {
      "error": "Google Flow account john@gmail.com Google rejected this account session (HTTP 401). We are automatically re-verifying it — please retry in about a minute. If the account was signed out, you will receive a reconnect email.",
      "code": 596
    }
    

Model

Every media item of the project, up to 25,000, each with its mediaGenerationId, plus the counts.

The project's media, field by field
{
  email: string                // Echo of the path parameter
  projectId: string            // The project read, whether passed or defaulted
  count: number                // Length of media[]
  likelyUploads: number        // How many entries have likelyUpload: true
  truncated?: true             // Present when the project holds more than the 25,000 entries returned
  media: [{                    // every media in the project, up to 25,000
    mediaGenerationId: string  // the media's id: send it in mediaGenerationIds of DELETE /assets/{email} to delete an image or video, or to GET /assets/{mediaGenerationId} to download it
    mediaType: 'IMAGE' | 'VIDEO' | 'OTHER'  // from Google's record; OTHER when it is neither
    createTime?: string        // ISO 8601, absent on records Google returns without one
    likelyUpload: boolean      // True when Google recorded this as an upload
  }]
}

Examples

  • TOKEN='YOUR_API_TOKEN'
    EMAIL='john@gmail.com'
    ENCODED=$(printf %s "$EMAIL" | jq -sRr @uri)
    
    # The account's current project
    RESP=$(curl -s -H "Authorization: Bearer $TOKEN" \
      "https://api.useapi.net/v1/google-flow/assets/media/$ENCODED")
    
    jq '{projectId, count, likelyUploads}' <<<"$RESP"
    
    # A specific project, listing the uploads oldest first
    PROJECT_ID='6db64a76-90a9-4ecd-99f0-cc524ec2b2af'
    
    curl -s -H "Authorization: Bearer $TOKEN" \
      "https://api.useapi.net/v1/google-flow/assets/media/$ENCODED?projectId=$PROJECT_ID" \
    | jq '[.media[] | select(.likelyUpload)] | sort_by(.createTime)
          | .[] | "\(.createTime)  \(.mediaType)  \(.mediaGenerationId)"' -r
    
  • const token = 'YOUR_API_TOKEN';
    const email = 'john@gmail.com';
    
    const params = new URLSearchParams();
    // Omit projectId to read the account's current project
    // params.set('projectId', '6db64a76-90a9-4ecd-99f0-cc524ec2b2af');
    
    const url = `https://api.useapi.net/v1/google-flow/assets/media/${encodeURIComponent(email)}`
      + (params.toString() ? `?${params}` : '');
    
    const resp = await fetch(url, { headers: { 'Authorization': `Bearer ${token}` } });
    if (!resp.ok) throw new Error(`${resp.status} ${await resp.text()}`);
    
    const { projectId, count, likelyUploads, media } = await resp.json();
    console.log(`${projectId}: ${count} media, ${likelyUploads} uploads`);
    
    const uploads = media
      .filter(m => m.likelyUpload)
      .sort((a, b) => (a.createTime ?? '').localeCompare(b.createTime ?? ''));
    
    for (const m of uploads.slice(0, 10))
      console.log(`${m.createTime}  ${m.mediaType}  ${m.mediaGenerationId}`);
    
  • import requests
    from urllib.parse import quote
    
    token = 'YOUR_API_TOKEN'
    email = 'john@gmail.com'
    
    url = f'https://api.useapi.net/v1/google-flow/assets/media/{quote(email, safe="")}'
    
    # Omit projectId to read the account's current project
    params = {}
    # params['projectId'] = '6db64a76-90a9-4ecd-99f0-cc524ec2b2af'
    
    resp = requests.get(url, headers={'Authorization': f'Bearer {token}'}, params=params)
    resp.raise_for_status()
    data = resp.json()
    
    print(f"{data['projectId']}: {data['count']} media, {data['likelyUploads']} uploads")
    
    uploads = sorted((m for m in data['media'] if m['likelyUpload']),
                     key=lambda m: m.get('createTime') or '')
    
    for m in uploads[:10]:
        print(f"{m.get('createTime')}  {m['mediaType']}  {m['mediaGenerationId']}")
    

Try It