PUT | /api/settings/keys | Update setting key |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
KeyGuid | body | Guid | No | |
Name | body | String | No | |
AccessType | body | String | No | Allowable Values
|
GroupGuid | body | Guid | No | |
Visibility | body | String | No | Allowable Values
|
Description | body | String | No | |
ValidationDescription | body | String | No | |
Label | 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/settings/keys HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"keyGuid": "00000000000000000000000000000000",
"name": "String",
"accessType": "String",
"groupGuid": "00000000000000000000000000000000",
"visibility": "String",
"description": "String",
"validationDescription": "String",
"label": "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" } } }