Navigation

Get an Atlas User by ID

Retrieve a Atlas user's profile using their unique identifier. You cannot use this endpoint to return information on an API Key. To return information on an API Key, use the Get One API Key endpoint.

Important With Circle IconCreated with Sketch.Important

You can always retrieve your own user account.

If you are the owner of an Atlas organization or project, you can also retrieve the user profile for any user with membership in that organization or project.

The Atlas API authenticates using HTTP Digest Authentication. Provide a programmatic API public key and corresponding private key as the username and password when constructing the HTTP request.

To learn how to configure API access for an Atlas project, see Configure Atlas API Access.

Info With Circle IconCreated with Sketch.Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project ID. For existing groups, your group/project ID remains the same. The resource and corresponding endpoints use the term groups.

Base URL: https://cloud.mongodb.com/api/atlas/v1.0

GET /users/{USER-ID}
Path ParameterTypeNecessityDescription
USER-IDstringRequiredUnique identifier of the user that you want to retrieve. If you know the user's Atlas username, use the /users/byName/{USER-NAME} endpoint to retrieve the user's profile and unique identifier.

This endpoint might use any of the HTTP request query parameters available to all Atlas API resources. All of these are optional.

NameTypeNecessityDescriptionDefault
prettybooleanOptionalFlag indicating whether the response body should be in a prettyprint format.false
envelopebooleanOptional

Flag indicating if Atlas should wrap the response in a JSON envelope.

This option may be needed for some API clients. These clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query.

For endpoints that return one result, the response body includes:

statusHTTP response code
envelopeExpected response body
false

This endpoint doesn't use HTTP request body parameters.

The JSON document contains each of the following elements:

Response ParameterTypeRequiredDescription
countrystringRequiredISO-3166-1 alpha 2 country code of the Atlas user's country of residence.
emailAddressstringRequiredAtlas user's email address.
firstNamestringRequiredAtlas user's first name.
idstringRequiredUnique identifier for the Atlas user.
lastNamestringRequiredAtlas user's last name.
linksarray of objectsRequiredOne or more links to sub-resources and/or related resources. The relation-types between URL s are explained in the Web Linking Specification.
mobileNumberstringRequiredAtlas user's mobile or cell phone number, if it is listed in the user's profile.
passwordstringRequired

Password. Atlas doesn't return this parameter except in response to creating a new user.

You cannot update the password via API once set. The user must log into Atlas and update their password from the Atlas console.

rolesarray of objectsRequiredEach object in the array represents either an Atlas organization or project the Atlas user is assigned to and the Atlas role has for the associated organization or project. You can specify either roles.orgId or roles.groupId per object.
roles.groupIdstringRequiredunique identifier of the project in which the user has the specified roles.roleName.
roles.orgIdstringRequiredunique identifier of the organization in which the user has the specified roles.roleName.
roles.roleNamestringRequired

name of the role.

When associated to roles.orgId, the valid roles and their mappings are:

RoleMapping
ORG_OWNEROrganization Owner
ORG_GROUP_CREATOROrganization Project Creator
ORG_BILLING_ADMINOrganization Billing Admin
ORG_READ_ONLYOrganization Read Only
ORG_MEMBEROrganization Member

When associated to roles.groupId, the valid roles and their mappings are:

RoleMapping
GROUP_OWNERProject Owner
GROUP_CLUSTER_MANAGERProject Cluster Manager
GROUP_READ_ONLYProject Read Only
GROUP_DATA_ACCESS_ADMINProject Data Access Admin
GROUP_DATA_ACCESS_READ_WRITEProject Data Access Read/Write
GROUP_DATA_ACCESS_READ_ONLYProject Data Access Read Only
teamIdsarray of stringsRequiredUnique identifiers for each team to which the user belongs.
usernamestringRequiredAtlas username. Must use email address formatting. You cannot modify the username once set.
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest --include \
--header "Accept: application/json" \
--header "Content-Type: application/json" \
--request GET "https://cloud.mongodb.com/api/atlas/v1.0/users/5af1c27a0a7fa48c76d3a761"
HTTP/1.1 401 Unauthorized
Content-Type: application/json;charset=ISO-8859-1
Date: {dateInUnixFormat}
WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false
Content-Length: {requestLengthInBytes}
Connection: keep-alive
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: application/json
Strict-Transport-Security: max-age=300
Date: {dateInUnixFormat}
Connection: keep-alive
Content-Length: {requestLengthInBytes}
1{
2 "emailAddress": "john.doe@example.com",
3 "firstName": "John",
4 "id": "5af1c27a0a7fa48c76d3a761",
5 "lastName": "Doe",
6 "links": [
7 {
8 "href": "https://cloud.mongodb.com/api/atlas/v1.0/users/5af1c27a0a7fa48c76d3a761",
9 "rel": "self"
10 },
11 {
12 "href": "https://cloud.mongodb.com/api/atlas/v1.0/users/5af1c27a0a7fa48c76d3a761/accessList",
13 "rel": "http://mms.mongodb.com/accessList"
14 }
15 ],
16 "mobileNumber" : "2125550198",
17 "roles": [
18 {
19 "orgId": "5af1c27a0a7fa48c76d3a762",
20 "roleName": "ORG_OWNER"
21 },
22 {
23 "groupId": "5af1c27a0a7fa48c76d3a763",
24 "roleName": "GROUP_OWNER"
25 }
26 ],
27 "teamIds": [
28 "5af1c27a0a7fa48c76d3a764"
29 ],
30 "username": "john.doe@example.com"
31}
Give Feedback