Get a user by id
Path parameters
Response
OK
Example response
{
"data": {
"_id": "65f1c2a4d8b9e0123456789a",
"firstName": "Ada",
"lastName": "Lovelace",
"email": "ada@example.com",
"role": [
"admin"
],
"teamId": "65f1c2a4d8b9e01234567890",
"createdAt": "2026-04-01T10:00:00.000Z",
"updatedAt": "2026-04-15T14:30:00.000Z"
}
}Changes
Changed in 3 of the 38 revisions of this API.368
- ▲
for the
pathrequest parameteruserId, the minLength was increased from0to1request-parameter-min-length-increased
- ▲
the response's body type/format changed from
/toobject/for status200response-body-type-changed
- ●
removed the optional property
detailsfrom the response with the403statusresponse-optional-property-removed
- ●
removed the optional property
detailsfrom the response with the404statusresponse-optional-property-removed
- ●
removed the optional property
detailsfrom the response with the500statusresponse-optional-property-removed
- ●
added the new
falseenum value to thesuccessresponse property for the response status403response-property-enum-value-added
- ●
added the new
falseenum value to thesuccessresponse property for the response status404response-property-enum-value-added
- ●
added the new
falseenum value to thesuccessresponse property for the response status500response-property-enum-value-added
- ○
removed
SuccessResponsesubschema #2from the response bodyallOflist for the response status200response-body-all-of-removed
- ○
added the non-success response with the status
401response-non-success-status-added
- ○
added the optional property
datato the response with the403statusresponse-optional-property-added
- ○
added the optional property
datato the response with the500statusresponse-optional-property-added
- ○
added the required property
datato the response with the200statusresponse-required-property-added
- ○
added the required property
msgto the response with the200statusresponse-required-property-added
- ○
added the required property
successto the response with the200statusresponse-required-property-added
This revision also has 27 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 18 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲