| PUT | /client/ClientUser |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| User | body | ClientUserApiModel | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| form | string | No | ||
| IsDeleted | form | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| AccountId | form | long | No | |
| form | string | No | ||
| Password | form | string | No | |
| IsAdministrator | form | bool | No | |
| IsSuperAdmin | form | bool | No | |
| PersonId | form | long | No | |
| IsClient | form | bool | No | |
| UserVerified | form | bool | No | |
| UserUnlocked | form | bool | No | |
| IsDeleted | form | bool | 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 /client/ClientUser HTTP/1.1
Host: api.helferportal.de
Accept: application/json
Content-Type: application/json
Content-Length: length
{"User":{"Id":0,"EMail":"String","IsDeleted":false}}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Id":0,"AccountId":0,"EMail":"String","Password":"String","IsAdministrator":false,"IsSuperAdmin":false,"PersonId":0,"IsClient":false,"UserVerified":false,"UserUnlocked":false,"IsDeleted":false}