Create a User
Roles
/v1/usersCreate a user.
- USER_CREATE_START
- USER_CREATE_SUCCESS
- USER_CREATE_FAIL
Authorization
bearerAuth In: header
Request Body
application/json
Create a User
User claims to be persisted. No claims are persisted by default. Consider PII implications before persisting any claims.
Authentication Provider information for the user. This enables linking the user to an external identity provider. If implemented insecurely, this process can be exploited by malicious actors to gain unauthorized access to legitimate user accounts.
To mitigate this risk, require authentication for both accounts involved in the link, whether the link is created manually or automatically. Always prompt the user to enter credentials to verify ownership before establishing the link.
Response Body
application/json
application/json
curl -X POST "https://example.vii.au01.mattr.global/v1/users" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "0c3fad74-a8df-4a2d-8e75-f2d356b413ba",
"claims": {
"externalUserId": "0c3fad74-a8df-4a2d-8e75-f2d356b413ba"
},
"authenticationProvider": {
"providerId": "41458e5a-9092-40b7-9a26-d4eb43c5792f",
"url": "https://example-university.au.auth0.com",
"subjectId": "example-university-oauth2|123456789"
}
}{
"code": "string",
"message": "string",
"details": [
{
"value": "string",
"msg": "Invalid value",
"param": "id",
"location": "body"
}
]
}How would you rate this page?
Retrieve authorization server metadata GET
Returns the OAuth 2.0 Authorization Server Metadata for your tenant. This is the standard OAuth 2.0 Well-Known endpoint, providing public metadata that describes the tenant’s OAuth 2.0 configuration and capabilities. https://www.rfc-editor.org/rfc/rfc8414.html
Retrieve all users GET
Returns a list of all users on your tenant. ### **Analytic events** * USER_RETRIEVE_LIST_START * USER_RETRIEVE_LIST_SUCCESS * USER_RETRIEVE_LIST_FAIL