Skip to main content
Is Entity Saved
Requires the entities bundle. A project without the entities bundle returns 403 database/tables-not-available. See Bundles.
Returns whether the specified entity is saved in any collection belonging to the authenticated user, along with the list of matching collections.

Query Parameters

string
required
The ID of the entity to check.
string
Service key only, and required with one: the user this request acts as, whose collections are checked. A user token always acts as its own user and must not send it (400 collection/acting-user-not-allowed).

Response

boolean
true if the entity is saved in at least one collection.
Array<{ id: string; name: string }>
List of collections (by ID and name) that contain this entity.

Error Responses

A service key sent no actingUserId.
A user token sent actingUserId, even naming its own user. Only a service key names the user it acts as; a user token always acts as its own user.
Returned when a service key names an actingUserId that isn’t a user in this project.
The request sent userId. On this route the user a service key acts as is actingUserId.With a service key:
With a user token, or with no credentials: