All messages can be collected periodically (every 30 minutes) and transmitted to your sFTP server by XML. Here, all the changes to transactions, orders, items, packages and errors are are collected on a queue, then bundled into one or more XML files for transmission.

The messages are provided in XML files separated/grouped by “order_type” (NORMAL, MANUAL, SAMPLE_INTERN, SAMPLE_CUSTOMER, TEST).

“order-type = NORMAL”

<unique_id_for_request_package>_<YYYYMMDDHHIISS>.xml

e.g. "1234567890_20130603220547.xml"

all other “order_type” values

<order_type>_<unique_id_for_request_package>_<YYYYMMDDHHIISS>.xml

e.g. "TEST_1234567890_20130603220547.xml"

YYYY: Year, 4 digits
MM: Month, 2 digits
DD: Day, 2 digits
HH: Hour, 2 digits
Minute, 2 digits
SS: Second, 2 digits

Current XSD: statusreporting_v2-3.xsd

Example XML: statusreporting_sample.xml

URL: tracking.pdi.elanders-germany.com
Port: 22
Protocols: sFTP, SCP
Authorized Keys: RFC 4716

You can choose between GET and POST for active responses (pushes). The use on your side of SSL (HTTPS) is possible in either case.

We store the URL of your interface in the project. Once an order's status changes, this is transmitted to you.

Expected return for GET / POST

To check whether the status transmission was successful, our system expects a success message and any error messages in the following form:

success=true&msg=your text

Notice: Push-Notifications are only available for very small projects and if a live feedback is mandatory (we charge extra costs for this service).