| PUT | /api/partners/{PartnerGuid} | Modify an existing Partner. | If left null, optional parameters will be ignored. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PartnerGuid | path | Guid | Yes | |
| PartnerName | body | string | No | |
| CompanyName | body | string | No | |
| ContactName | body | string | No | |
| Status | body | string | No | Allowable Values
|
| 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/partners/{PartnerGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"partnerGuid": "00000000000000000000000000000000",
"partnerName": "String",
"companyName": "String",
"contactName": "String",
"status": "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"
}
}
}