Description
You have to call this method when you want to edit info of an existing user in DRUID.
If you edit any confirmable id (email, mobile), and user had that id previously confirmed, new id need to be confirmed. The user’s new email/mobile will not be established until the confirmation process is completed.
Please, read first https://dru-id.com/developers/apis/oauth-2/ to learn about Oauth2 protocol and the meaning of each token.
Warning!: this is a replacement operation. Any data that the user already has and is not sent in the request will be removed from the user. Please check that the json is well formed before making the call to avoid possible unwanted data loss.
Endpoint URL:
POST https://{your-endpoint-domain.com}/activityid/v1/user/update
Request parameters
Parameter | Description | Type | Required |
---|---|---|---|
Authorization | Bearer ${access_token}
Literal text Bearer followed by access_token that is the token for current logged user obtained from login endpoint | string | yes |
Content-Type | application/json | string | yes |
Accept | application/json | string | yes |
From | Id of the entry point | string | yes |
Accept-Language | Language of this request | Locale | no |
Query string parameters
Parameter | Description | Type | Required |
---|
Request example
Parameter | Description | Type | Required | Value |
---|---|---|---|---|
actor.id | app_id of the application you are using to log user | string | yes | app id |
actor.objectType | Type of the object which represents the actor. | string | yes | ‘application’ |
verb | Verb used for create user | string | yes | ‘create’ |
object.objectType | ObjectType represents the user | string | yes | ‘user’ |
object.password | Password of the user. it must be send plain | string | yes | user password |
object.ids | User identifiers. More info about user identifiers User Info | struct | yes | struct |
object.datas | User datas. More info about user datas User Info | struct | yes | struct |
object.addresses | User addresses. More info about user addresses User Info | struct | no | struct |
object.assertions | Struct that defines legalities manage by the user. More info about user assertions User Info | struct | yes | struct |
source.id | Type of device doing the activity | string | yes | ‘unknown’ | ‘pc’ | ‘mobile’ | ‘tablet’ | ‘game_console’ | ‘itv’ |
source.objectType | Type of source | string | yes | ‘device’ |
Response examples
Response: user updated successfully
Response: user updated successfully, and email or mobile needs confirmation
Response: no changes in update
You will receive Http Response 304 Not Modified
Response: Errors in request
Response codes
Code | Type | Description |
---|---|---|
200 | Success | User updated successfully. You will get ‘user logged JSON response’ |
206 | Success | Partial content: User updated successfully but needs some data to be completed |
304 | Success | User not modified. There is no need to apply any changes. |
400 | Error | Bad Request: The request could not be understood by the server due to malformed syntax |
401 | Error | Unauthorized: authentication is required and has failed or has not yet been provided (token is invalid, etc) |
403 | Error | Forbidden: user id or password are invalid |
404 | Error | User not found |
416 | Error | Some of the fields to update do not comply with the required specifications |
428 | Error | Precondition required: User need to configure MFA or needs to send a MFA code. Check the MFA API |
500 | Error | Internal Server Error: The server encountered an unexpected condition which prevented it from fulfilling the request |