Authorization header.
List Users
Retrieve a paginated list of all users in your workspace. Use the query parameters below to filter results by role or account status.GET https://api.google.com/v1/users
Query Parameters
The page number to retrieve. Defaults to
1.Number of users to return per page. Defaults to
20. Maximum is 100.Filter by user role. Accepted values:
admin, editor, viewer.Filter by account status. Accepted values:
active, inactive.Example Request
Example Response
Response Fields
Indicates whether the request completed successfully.
Array of user objects matching the query.
Pagination metadata including
page, per_page, and total record count.Get User
Fetch the full profile for a single user by their unique ID.GET https://api.google.com/v1/users/:id
Path Parameters
The unique identifier of the user (e.g.,
usr_abc123).Example Request
Example Response
Create User
Invite a new user to your workspace by providing their email address, display name, and assigned role.POST https://api.google.com/v1/users
Body Parameters
The email address of the new user. Must be unique within the workspace.
The display name for the user.
The role to assign to the user. Accepted values:
admin, editor, viewer.Example Request
Example Response
A welcome email is automatically sent to the new user upon successful creation. The user’s account is immediately active.
Update User
Modify one or more fields on an existing user. Only include the fields you want to change — all other fields remain unchanged.PATCH https://api.google.com/v1/users/:id
Path Parameters
The unique identifier of the user to update.
Body Parameters
Updated display name for the user.
Updated role. Accepted values:
admin, editor, viewer.Updated account status. Accepted values:
active, inactive.Example Request
Example Response
Remove User
Permanently remove a user from your workspace.DELETE https://api.google.com/v1/users/:id
Path Parameters
The unique identifier of the user to remove.
Example Request
Example Response
A successful deletion returns an HTTP204 No Content response with an empty body, confirming the user has been removed.
Error Reference
400 Bad Request
400 Bad Request
The request body is missing required fields or contains invalid values. Check that
email, name, and role are all provided when creating a user.401 Unauthorized
401 Unauthorized
404 Not Found
404 Not Found
No user exists with the specified
id. Verify the ID and try again.409 Conflict
409 Conflict
A user with the given email address already exists in the workspace.
422 Unprocessable Entity
422 Unprocessable Entity
The request was well-formed but contains semantic errors, such as an unrecognized role or status value.