Receiving data
This chapter describes how realization data messages can be received.
To receive the realization data messages generated by the app, you need to develop an API that can be called by the FleetGO backend.
There is no predefined format for the API. The table below contains a possible structure of an endpoint that can be used by the FleetGO backend for sending realization data messages. Feel free to deviate from this example as long as the API accepts the messages defined in the Realization data chapter.
Method | POST |
|---|---|
Endpoint | {baseUrl}/api/RealizationData |
Headers |
|
Body | This is just an example of the request body to expect. {
"type": "Entity",
"data": {
"foreignId": "1234-1",
"flag": "stop",
"checkout": {
"arrival": "2024-01-17T08:52:06.388Z",
"signOff": "2024-01-17T09:12:47.153Z",
"questionnaire": {
"shipment_unloaded": false,
"not_unloaded_reason": "Goods damaged",
"damage_description": "Example description of the damage"
}
}
},
"location": {
"latitude": 52.2531361,
"longitude": 5.4890928,
"speedMs": 25,
"bearing": 75.0
},
"origin": {
"appId": 60000153,
"deviceId": "358240051111110",
"driverNumber": "110",
"coDriverNumber": null
},
"vehicle": {
"licensePlate": "TE-ST-12",
"odometer": 250030
},
"messageTime": "2024-01-17T09:12:47.841Z"
} |
Polling
Although strongly discouraged, there is an API available for polling data. The API-specification of the polling API can be found at https://data2tracktrip.docs.apiary.io/#/reference/realization-data