Chelabase
ManagementApp users

List a project's users

GET
/v1/projects/{id}/users

50 per page. search matches part of the email, ignoring case.

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string

Project id

Formatuuid

Query Parameters

search?string

Part of an email

page_token?string

next_page_token of the previous page

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/users"
{  "next_page_token": "string",  "users": [    {      "created_at": "2019-08-24T14:15:22Z",      "email": "string",      "email_verified": true,      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "state": "active"    }  ]}

Enable app users, or change their settings PUT

With no settings yet this enables app users: it checks the database, the data API on every branch and the table, then answers 202 and the worker creates the project's identity pool, the users table and its guard. Pressing it again while `enabling`, or after `failed` (same location), starts the work again (202), and so does pressing it on a disable on hold (`disabling` with an `error`: its pool still has users), which keeps the pool and its users. Once enabled it changes `email_verification` and `on_delete` only (200); another location is 409 `app_users_location_fixed`.

Create a user POST

Creates the identity user, then writes the user's row to the users table and commits. When the table refuses the row (its own constraints) the identity user is deleted again. Columns of your own get their defaults.