Users

Getting User details

Typically, you supply the integer ID to get information about the user associated with that id.

It is also possible to supply the text current instead of an integer ID; please see the following endpoint for documentation about this.

get/v1/users/{actorId}

Path parameters

actorIdstring required

Typically the integer ID of the User. For getting user details, you can also supply the text current, which will tell you about the currently authenticated user.

Response

OK

createdAtstring required

ISO date format

displayNamestring required

All Actors, regardless of type, have a display name

idnumber required
type'user' | 'field_key' | 'public_link' | 'singleUse' required

the Type of this Actor; typically this will be user.

updatedAtstring

ISO date format

deletedAtstring

ISO date format

emailstring required

Only Users have email addresses associated with them

Changes

Changed in 3 of the 54 revisions of this API.4

    • api operation id Getting User details removed and replaced with getUserDetails

      api-operation-id-removed

    • removed the non-success response with the status 403

      response-non-success-status-removed

    • api operation id getUserDetails removed and replaced with Getting User details

      api-operation-id-removed

    • added the non-success response with the status 403

      response-non-success-status-added

    This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog