| PUT | /api/services/{ServiceGuid}/users/password | Change the password of a service user | Change the password of a service user. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ServiceGuid | path | Guid | Yes | |
| ServiceUserGuid | query | Guid | No | Only required if EmailAddress is not supplied. |
| EmailAddress | query | String | No | Only required if ServiceUserGuid is not supplied. |
| OldPassword | body | String | Yes | Old password for the service user. |
| NewPassword | body | String | Yes | New password for the service user. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /api/services/{ServiceGuid}/users/password HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"serviceGuid": "00000000000000000000000000000000",
"serviceUserGuid": "00000000000000000000000000000000",
"emailAddress": "String",
"oldPassword": "String",
"newPassword": "String"
}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{
"responseStatus": {
"errorCode": "String",
"message": "String",
"stackTrace": "String",
"errors": [
{
"errorCode": "String",
"fieldName": "String",
"message": "String",
"meta": {
"String": "String"
}
}
],
"meta": {
"String": "String"
}
}
}