PUT | /api/sites/endpoints/{EndpointGuid} | Update Site Endpoint |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
EndpointGuid | path | Guid | Yes | |
Name | body | String | No | |
SiteVersion | body | String | No | |
Description | body | String | No | |
Url | body | String | No | |
SiteExternalCertStoreLocation | body | String | No | |
SiteExternalPrivateKeyCertThumbprint | body | String | No |
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/sites/endpoints/{EndpointGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"endpointGuid": "00000000000000000000000000000000",
"name": "String",
"siteVersion": "String",
"description": "String",
"url": "String",
"siteExternalCertStoreLocation": "String",
"siteExternalPrivateKeyCertThumbprint": "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" } } }