Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
API integration for recurring courier jobs
Explains how an API automates recurring courier jobs: bookings, shipment data, tracking and billing. Practical data flows and integration points for Swiss businesses.
Quick answer
An API automates recurring courier jobs by sending bookings, shipment details, tracking status and billing data directly between your systems and x25pronto. This reduces manual work, cuts errors and gives you better control over volume and costs.
When to choose an API integration
Choose an API when you run frequent one‑off or scheduled courier jobs. Common examples: spare parts, urgent documents, production supplies or returns. If manual bookings are a bottleneck or you need ERP/WMS connectivity, an API improves speed and accuracy.
Which processes you can automate
Key processes: creating requests (pickup, recipient, time window), label generation and packing instructions, live tracking and status updates, plus billing and invoice data. You can also automate exception handling such as delays, address validation or returns.
Typical data exchanged
Frequent fields: sender and recipient addresses (include company IDs where relevant), pickup time windows, parcel dimensions and contents, order/reference numbers, requested services (extra stops, priority), tracking IDs and status codes, invoice references and cost centres.
Technical highlights of a practical API
Modern APIs use REST/JSON, HTTPS and token‑based authentication (OAuth2 or API keys). Useful endpoints include /createBooking, /cancelBooking, /getTracking, /getRates and /getInvoice. Webhooks provide real‑time events like "picked_up" or "delivered".
Error handling and validation
Validate addresses and parcel data before creating bookings. Implement retries for timeouts and return clear error codes for bad input. Logging and audit trails simplify troubleshooting and support billing disputes.
Connecting ERP, WMS and e‑commerce
Link the API to your ERP for automatic invoice mapping and cost allocation. In a WMS, trigger pickups when orders reach shipping status. E‑commerce systems can use webhooks to send customers tracking links instantly.
Frequently asked questions
What security measures are needed for API use?
Use HTTPS, strong API keys or OAuth2 and assign minimal privileges per key. Implement IP whitelisting and role controls. Avoid storing unnecessary sensitive data to reduce risk.
How long does integration take?
Simple integrations can take a few days to two weeks. Complex ERP connections with testing and approvals can take several weeks. Timeline depends on internal IT resources and testing cycles.
What tracking info does the API provide?
The API provides status codes (accepted, picked_up, in_transit, delivered), timestamps, location updates and, when available, proof of delivery or recipient signature. Webhooks push these to your system in real time.
How is billing automated via API?
The API sends billing details such as shipment ID, tariff, cost centre and invoice reference. Periodic queries or webhook events provide invoice IDs and PDF receipts for automatic posting in your finance system.