/em/oem/telematic/trigger

The following routes are available for this service:
DELETE	/em/oem/telematic/trigger	Delete specified triggers	irgendein Text

Parameters:
Name	Parameter	Data Type	Required	Description
Triggers	body	TelematicTrigger	Yes	Get provider specific telematic data
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

HTTP + JSON Request

The following are sample HTTP requests. The placeholders shown need to be replaced with actual values.

GET /em/oem/telematic/trigger HTTP/1.1 
Host: eta.cloud.ptvgroup.com 
Content-Type: application/json
Content-Length: length

{
  "triggers": [
    {
      "telematicProvider": "String",
      "agheeraTrigger": {
        "fleetName": "String",
        "vehicleId": "String",
        "start": "0001-01-01T00:00:00+00:00",
        "end": "0001-01-01T00:00:00+00:00",
        "callBack4Telematic": {
          "url": "String",
          "password": "String",
          "user": "String"
        },
        "scemid": "String",
        "licencePlate": "String",
        "pollingInterval": 0,
        "tripId": "String"
      }
    }
  ],
  "token": "String",
  "source": "String"
}

HTTP + JSON Response

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"
    }
  }
}