List app users
<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>
Returns the app's users: the people who signed up to it, or who accepted an invitation and signed in. Someone you've invited who hasn't signed in yet isn't listed.
It leaves out accounts Base44 added to the app on its own, such as workspace admins and support staff granted access, and the short-lived accounts a test run creates. Unless your own account has a Base44 or Wix email address, Count app users also leaves out accounts with one. This list includes them, so the two can differ. Row-level security on the User entity applies, so rules that narrow reads narrow this list too.
Filter with q, or by passing a field name directly as a query parameter for an exact match, as in ?role=admin. Users come back in the order they joined unless you set sort.
<Warning>Each user includes fields beyond the ones documented here. Don't rely on undocumented response fields, as they can change at any time.</Warning>
<Note>This endpoint accepts a personal API key belonging to a user with editor access to the app, including a read-only key. Workspace API keys are not accepted.</Note>
Path parameters
ID of the app whose users you want to list.
ID of the app whose users you want to list.
Query parameters
Filter as a JSON object of field names and values, for example {"status": "paid"} for an exact match, or using an operator such as $gt for a comparison. See Filtering, sorting, and paging for a full list of operators.
Maximum number of users to return, from 1 to 10000. Leave it out to get every matching user in one response.
Number of users to skip before the ones you get back, 0 or more. Defaults to 0. Use it with limit to page through a long list.
Single field to sort by, prefixed with - for descending. For example, -created_date returns newest first. Sorting by more than one field isn't supported.
Comma-separated list of fields to return, which reduces the response size on a wide entity. Reach a field inside an object with dots, as in customer.email. Each record still carries its id whether you ask for it or not.
Response
The app's users.
Example response
[
{
"id": "6874b0c2e1a94d0031bb77de",
"email": "jane@acme.com",
"full_name": "Jane Cooper",
"role": "user",
"collaborator_role": "editor",
"created_date": "2026-06-01T09:23:41.481000Z",
"updated_date": "2026-06-04T14:07:02.115000Z"
}
]Changes
Changed in 1 of the 14 revisions of this API.1
- ○
endpoint added
endpoint-added
- ○