| Required role: | Business |
| POST | /profile/delete |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserHasConfirmed | body | bool | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserThatWasDeleted | form | BusinessUserDto | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| form | string | No | ||
| FirstName | form | string | No | |
| LastName | form | string | No | |
| MobilePhone | form | string | Yes | |
| LegalIdentityVerified | form | bool | No | |
| Locale | form | Locale | No |
| EnUs | |
| NbNo |
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.
POST /profile/delete HTTP/1.1
Host: business-api.brovs.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userHasConfirmed":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"userThatWasDeleted":{"id":0,"email":"String","firstName":"String","lastName":"String","mobilePhone":"String","legalIdentityVerified":false,"locale":"EnUs"}}