110 lines
4.2 KiB
Plaintext
110 lines
4.2 KiB
Plaintext
|
||
|
||
Dear Gorka,
|
||
thanks for your reply!
|
||
|
||
We have a standard API that we provide openly - please see the attached documentation for more details.
|
||
The attached document also includes the URL and apikey for our TEST instance.
|
||
|
||
- endpoint URL for test and production
|
||
|
||
PROD URL: https://push-dhl.agheera.com/Telematics/positions
|
||
apiKey for Abian: 2NL7G-0QTMP-T0N54-7ERGY-S7U6U-SXKWF
|
||
TEST URL: https://push-test.agheera.com/Telematics/Positions
|
||
apiKey for testing purposes: 0eec610a-aad5-4f60-91c7-7f9a4089d5b5
|
||
|
||
- authentication method and credentials process
|
||
Authentication is done by sending an apikey in a HTTP header "apiKey" with each request.
|
||
There is no further handshake (oauth flow or similar). If the apikey is correct and accepted, data will be assigned to the customer (in this case Abian)
|
||
Apikey is provided by Agheera on request.
|
||
1 Apikey is bound to 1 customer and 1 environment (prod/test).
|
||
|
||
- required payload format
|
||
Please see attached documentation for more details.
|
||
We encourage to send data batches whenever possible.
|
||
|
||
- required vehicle identifier: license plate, device ID, MSISDN, etc.
|
||
Device ID and License Plate shall both be provided
|
||
|
||
- timestamp format/timezone
|
||
Must be in UTC timezone
|
||
Format: yyyy-MM-ddTHH:mm:ssZ
|
||
|
||
- required fields for position updates
|
||
Minimum required are: latitude, longitude, vehicleid(deviceid), licensePlate, measurementTime
|
||
We appreciate the following fields to have better Trip ETA calculation: speed, direction, assetType
|
||
|
||
- expected response codes
|
||
200 - OK
|
||
If data was accepted and was syntactically correct
|
||
400 - Bad request
|
||
If data was syntactically wrong/malformed
|
||
401 - Unauthorized
|
||
Wrong apikey or apikey header missing
|
||
405 - Method not available
|
||
If request method was not POST
|
||
|
||
- retry/error handling recommendations
|
||
We are not validating the semantics of position data at the point of response generation, so we return 200 - OK on almost all requests unless the request is badly malformed or unauthorized.
|
||
This also means a retry is not very likely needed, unless the Agheera server is down.
|
||
For sending position data to us, it is fine to "fire and forget" and not schedule a retry.
|
||
In case you notice any errors, please contact ops@agheera.com and we will investigate.
|
||
|
||
- whether positions should be sent only for active DHL trips/customer id 532 or for all authorized vehicles
|
||
Agheera does already filter the data so that DHL can only see data that is relevant for DHL trips.
|
||
So as far as we are concerned, you can send for all vehicles, and we will filter it anyway.
|
||
But I think this should be decided by ABIAN if they want this.
|
||
|
||
- any IP allowlist requirements
|
||
No IP whitelist in place. We do not need to know your IPs upfront.
|
||
|
||
|
||
Let me know if you have any open questions!
|
||
|
||
Kind Regards / Freundliche Grüße
|
||
Stephan Wahlen
|
||
Head of IoT Hardware
|
||
Agheera GmbH – a DHL Group company
|
||
|
||
stephan.wahlen@agheera.com
|
||
+49 2203 29757-23
|
||
Office: August-Horch-Straße 5, 51149 Köln
|
||
Warehouse: Kasinostraße 24, 53840 Troisdorf, Deutschland
|
||
Registered office Cologne; Register court Bonn; HRB 18111
|
||
VAT ID no. DE 273 231 181
|
||
Managing Directors: Pierre Lynch, Sven Kefferpütz
|
||
|
||
|
||
|
||
-----Ursprüngliche Nachricht-----
|
||
Von: Gorka Leceta <gleceta@roganet.es>
|
||
Gesendet: Donnerstag, 28. Mai 2026 11:52
|
||
An: Operations <ops@agheera.com>; Stephan Wahlen <stephan.wahlen@agheera.com>
|
||
Betreff: ABIAN SERVICE - Agheera Push API documentation request for GPS position integration
|
||
|
||
Hello Stephan / Agheera team,
|
||
|
||
We are Roganet, GPS provider for ABIAN SERVICE.
|
||
|
||
ABIAN has asked us to integrate active position pushing from their mobile app backend to Agheera for DHL transports.
|
||
|
||
Could you please send us the technical documentation for Agheera's push API?
|
||
|
||
We need:
|
||
- endpoint URL for test and production
|
||
- authentication method and credentials process
|
||
- required payload format
|
||
- required vehicle identifier: license plate, device ID, MSISDN, etc.
|
||
- timestamp format/timezone
|
||
- required fields for position updates
|
||
- expected response codes
|
||
- retry/error handling recommendations
|
||
- whether positions should be sent only for active DHL trips/customer id
|
||
532 or for all authorized vehicles
|
||
- any IP allowlist requirements
|
||
|
||
ABIAN registration was submitted on 2024-01-23 and the authorization document is AFTemplateV2-ABIAN SERVICE_2024-01-23T11_55_17Z.PDF.
|
||
|
||
Kind regards
|
||
|