Skip to main content
POST
Streamed List Objects (All Syncs)
Use this endpoint to enumerate every object a principal user can access across all syncs associated with a Connected User. This is useful when your app connects a user to multiple File Storage syncs, and you want a single list of permitted document IDs to feed into a search or vector index filter. For queries against a single Sync, use the sync-scoped Streamed List Objects endpoint instead.

Response format

The response is sent as application/x-ndjson with Transfer-Encoding: chunked. Each line of the response body is a JSON object tagged with the source syncInstanceId and integration. Success lines include an object field, whose value is the UUID of a Synced Object the user has access to with the specified role:
If a specific sync fails to enumerate (for example, its authorization store is temporarily unavailable), a single line with an error field is emitted for that sync and the stream continues with the remaining syncs:
Parse the response one line at a time. Each line is independently valid JSON; the response body as a whole is not.

Notes

  • Only syncs that belong to the authenticated Connected User and project are queried. Syncs without an authorization store (for example, integrations that do not support Permissions API) are skipped silently.
  • Per-sync errors do not abort the stream — inspect each line for an error field so that you can retry or surface individual failures without discarding results from successful syncs.

Authorizations

Authorization
string
header
required

Paragon User Token. Add to the Authorization header of your requests.

Body

application/json
objectType
enum<string>
required

The type of object to list.

Available options:
file,
folder
Example:

"file"

user
string
required

The email of the user to list accessible objects for.

role
enum<string>
required

The role to use for identifying accessible objects.

Available options:
can_read,
can_write,
is_owner
Example:

"can_read"

Response

A newline-delimited JSON stream. Each line is a JSON object tagged with syncInstanceId and integration. Success lines include an object field with the UUID of a Synced Object the user has access to. If a specific sync fails to enumerate, a line with an error field is emitted for that sync instead, and the stream continues with the remaining syncs.

The response is of type string.