...
# | Method | URL (after /pl/api/) / Description | Example - Request | Example - Response | |||||
---|---|---|---|---|---|---|---|---|---|
1 | 🔓 | POST | v-1/auth/generate Fetches an login-token that the application can use to gain access to the API. |
|
| ||||
2 | 🔒 | POST | v-1/routePlan Create an empty route plan (for a given distribution date). Create a route plan for each area (each plan has a given start-point). |
|
| ||||
3 | 🔒 | POST | v-1/routePlan/<rp_id>/customerSystem/<cs_id> Create an empty file (prepare for a file-upload). Step 1 in file upload. |
|
| ||||
4 | 🔒 | POST | v-1/file/<f_id> Upload the content of the file you have prepared. Filetypes supported:
Mimetype: multipart/form-data Name the file-field: "file". See file specification. Step 2 in file upload. |
| |||||
5 | 🔒 | GET | v-1/customerSystem/<cs <cs_id>/publishedOrders/<yyyy-mm-dd> Fetch the published orders including the routename of each order. Included for each order is an estimate for WHEN the order will be delivered. It's a time interval like this: HH:MM-HH:MM. This will return orders across many routePlans, but only from published plans for the given distribution-date. Assumes that imported customers/deliveries used the ORDER_ID field. | List of orders
|
...