GetUser - Amazon Chime SDK


Retrieves details for the specified user ID, such as primary email address, license type,and personal meeting PIN.

To retrieve user details with an email address instead of a user ID, use the ListUsers action, and then filter by email address.

Request Syntax

GET /accounts/accountId/users/userId HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.


The Amazon Chime account ID.

Pattern: .*\S.*

Required: Yes


The user ID.

Pattern: .*\S.*

Required: Yes

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 Content-type: application/json { "User": { "AccountId": "string", "AlexaForBusinessMetadata": { "AlexaForBusinessRoomArn": "string", "IsAlexaForBusinessEnabled": boolean }, "DisplayName": "string", "InvitedOn": number, "LicenseType": "string", "PersonalPIN": "string", "PrimaryEmail": "string", "PrimaryProvisionedNumber": "string", "RegisteredOn": number, "UserId": "string", "UserInvitationStatus": "string", "UserRegistrationStatus": "string", "UserType": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


The user details.

Type: User object


For information about the errors that are common to all actions, see Common Errors.


The input parameters don't match the service's restrictions.

HTTP Status Code: 400


The client is permanently forbidden from making the request.

HTTP Status Code: 403


One or more of the resources in the request does not exist in the system.

HTTP Status Code: 404


The service encountered an unexpected error.

HTTP Status Code: 500


The service is currently unavailable.

HTTP Status Code: 503


The client exceeded its request rate limit.

HTTP Status Code: 429


The client is not currently authorized to make the request.

HTTP Status Code: 401


In the following example or examples, the Authorization header contents( AUTHPARAMS ) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.


This example lists details for the specified user.

Sample Request

GET /console/accounts/12a3456b-7c89-012d-3456-78901e23fg45/users/1ab2345c-67de-8901-f23g-45h678901j2k HTTP/1.1 Host: Accept-Encoding: identity User-Agent: aws-cli/1.16.83 Python/3.6.6 Windows/10 botocore/1.12.73 X-Amz-Date: 20190108T180643Z Authorization: AUTHPARAMS

Sample Response

HTTP/1.1 200 OK x-amzn-RequestId: 6d2ef025-d8a7-42f4-8170-84cb09b70d3d Content-Type: application/json Content-Length: 562 Date: Tue, 08 Jan 2019 18:06:43 GMT Connection: keep-alive {"User": {"AccountId": "12a3456b-7c89-012d-3456-78901e23fg45","Delegates": null,"Devices": null,"DisplayName": "user1 user1","EmailAlias": [],"FullName": "user1 user1","InvitedOn": null,"IsProTrial": false,"LastActiveOn": null,"LicenseType": "Pro","PersonalPIN": "XXXXXXXXXX","PresenceVisibility": "Public","PrimaryEmail": "","PrimaryProvisionedNumber": null,"RegisteredOn": "2018-12-20T18:45:25.231Z","UserId": "1ab2345c-67de-8901-f23g-45h678901j2k","UserInvitationStatus": null,"UserLocale": null,"UserRegistrationStatus": "Registered","Vanity": null} }

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: