Log in
Request body
Response
OK
Example response
{
"data": {
"user": {
"_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"
},
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}
}Changes
Changed in 3 of the 38 revisions of this API.11925
- ▲
the
passwordrequest property's minLength was increased from0to1request-property-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 the401statusresponse-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 status401response-property-enum-value-added
- ●
added the new
falseenum value to thesuccessresponse property for the response status500response-property-enum-value-added
- ○
request body became optional
request-body-became-optional
- ○
the
passwordrequest property type/format was generalized fromstring/passwordtostring/request-property-type-generalized
- ○
removed
SuccessResponsesubschema #2from the response bodyallOflist for the response status200response-body-all-of-removed
- ○
removed the non-success response with the status
422response-non-success-status-removed
- ○
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
- ▲
- ▲
request body became required
request-body-became-required
- ▲
the response's body type/format changed from
object/to/for status200response-body-type-changed
- ●
removed the optional property
datafrom the response with the200statusresponse-optional-property-removed
- ●
removed the optional property
msgfrom the response with the200statusresponse-optional-property-removed
- ●
removed the optional property
successfrom the response with the200statusresponse-optional-property-removed
- ○
added
SuccessResponsesubschema #2to the response bodyallOflist for the response status200response-body-all-of-added
- ○
added the non-success response with the status
401response-non-success-status-added
- ○
added the optional property
detailsto the response with the422statusresponse-optional-property-added
- ○
added the optional property
detailsto the response with the500statusresponse-optional-property-added
- ○
the response property
msgbecame required for the status422response-property-became-required
- ○
the response property
msgbecame required for the status500response-property-became-required
- ○
the response property
successbecame required for the status422response-property-became-required
- ○
the response property
successbecame required for the status500response-property-became-required
- ○
the
successresponse's property default valuefalsewas removed for the status422response-property-default-value-removed
- ○
the
successresponse's property default valuefalsewas removed for the status500response-property-default-value-removed
This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ▲
the
passwordrequest property type/format changed fromstring/tostring/passwordrequest-property-type-changed
- ▲
the response property
databecame optional for the status200response-property-became-optional
- ▲
the response property
msgbecame optional for the status200response-property-became-optional
- ▲
the response property
msgbecame optional for the status500response-property-became-optional
- ▲
the response property
successbecame optional for the status200response-property-became-optional
- ▲
the response property
successbecame optional for the status500response-property-became-optional
- ▲
removed the required property
data/userfrom the response with the200statusresponse-required-property-removed
- ●
removed the optional property
datafrom the response with the500statusresponse-optional-property-removed
- ●
removed the optional property
data/tokenfrom the response with the200statusresponse-optional-property-removed
- ○
the
passwordrequest property's minLength was decreased from1to0request-property-min-length-decreased
- ○
added the non-success response with the status
422response-non-success-status-added
- ○
removed the non-success response with the status
401response-non-success-status-removed
- ○
the
successresponse's property default valuefalsewas added for the status500response-property-default-value-added
- ○
the
successresponse's property default valuetruewas added for the status200response-property-default-value-added
- ○
removed the
falseenum value from thesuccessresponse property for the response status500response-property-enum-value-removed
- ○
removed the
trueenum value from thesuccessresponse property for the response status200response-property-enum-value-removed
This revision also has 18 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲