DELETE | /em/oem/config/{ConfigToken} | Delete one or all existing applications config | Delete config |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ConfigName | query | No | ConfigName for config | |
ConfigToken | path | Yes | Securtiy token, used on creating the app configs | |
DeleteAll | query | bool | No | Activate this to delete all configs with this token! |
Source | query | string | No | Name of the event provider: Examples are ptvemapp, ptvemportal, jmeter, any customer specific app |
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. The placeholders shown need to be replaced with actual values.
DELETE /em/oem/config HTTP/1.1
Host: eta.cloud.ptvgroup.com
Content-Type: application/json
Content-Length: length
{
"configName": "String",
"configToken": "String",
"deleteAll": false,
"source": "String"
}
The following are sample HTTP responses. The placeholders shown need to be replaced with actual values.
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "configNames": [ "String" ], "config": { "configName": "String", "revision": 0, "settings": {}, "configToken": "String" }, "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }