GET | /api/collections/settings/defaults |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
EntityGuid | path | Guid | No | |
Names | path | String[] | No | |
IgnoreHierarchy | path | Boolean | No | |
IgnoreUndefinedValues | path | Boolean | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Settings | form | List<Setting> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Name | form | string | No | |
Description | form | string | No | |
Group | form | string | No | |
AccessType | form | string | No | |
Value | form | string | No | |
EntityAccessType | form | string | No | |
EntityGuid | body | Guid | 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.
GET /api/collections/settings/defaults HTTP/1.1 Host: api.secure-messaging.com Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "settings": [ { "name": "String", "description": "String", "group": "String", "accessType": "String", "value": "String", "entityAccessType": "String", "entityGuid": "00000000000000000000000000000000" } ], "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }