PUT | /em/tour/batch/telematic | Alter telematic information for the tours | Alter telematic information for the tours |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
SCEMIDS | query | Yes | comma seperated list of tour scemids | |
TelematicData | body | TelematicData | Yes | Telematic Data for the tour(s) |
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.
PUT /em/tour/batch/telematic HTTP/1.1
Host: eta.cloud.ptvgroup.com
Content-Type: application/json
Content-Length: length
{
"scemids": [
"String"
],
"telematicData": {
"provider": "String",
"vehicleId": "String",
"startTime": "0001-01-01T00:00:00+00:00",
"endTime": "0001-01-01T00:00:00+00:00"
},
"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" } } }