GET | /em/analytics/data/tourlist | If not set configurations are used from the DAveCache |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
From | query | No | Timewindow from | |
Until | query | No | Timewindow until | |
SCEMIDs | query | No | Optional, comma separated list of tour SCEMIDs | |
SortOrderTourCreationTime | query | No | Sort by TourCreationTime. Possible values ASC or DESC, if not set or unknown DEFAULT=DESC | |
ItemsPerPage | query | No | Max results per page (Max. 50) | |
StartIndex | query | No | Skip the first n result. Index starts with 0. | |
Token | query | Yes | The security 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.
GET /em/analytics/data/tourlist HTTP/1.1
Host: eta.cloud.ptvgroup.com
Content-Type: application/json
Content-Length: length
{
"from": "0001-01-01T00:00:00+00:00",
"until": "0001-01-01T00:00:00+00:00",
"scemiDs": [
"String"
],
"sortOrderTourCreationTime": "String",
"itemsPerPage": 0,
"startIndex": 0,
"token": "String",
"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 { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } }, "tourData": [ {} ], "currentItemCount": 0, "itemsPerPage": 0, "startIndex": 0, "totalItems": 0 }