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 automated courier bookings: setup and benefits
Explains how the x25pronto API works, authentication methods, booking and reporting endpoints, and typical integration timeframes for businesses in Switzerland.
Quick answer
The x25pronto API lets your IT systems create courier bookings automatically. Authenticate with an API key/token, send booking data to the booking endpoint, and retrieve status or reports from reporting endpoints. Typical integration times range from 1–4 weeks depending on scope, reducing manual booking tasks across Switzerland.
What the x25pronto API does
The API links your ERP, WMS or order system directly to x25pronto booking services. It transmits pickup and delivery addresses, parcel dimensions, time windows and recipient details. You trigger single or batch courier jobs without manual entry in a web portal.
Authentication and security
Access uses an API key and token-based authentication over HTTPS/TLS. Role-based permissions limit which endpoints your system can call. We recommend IP whitelisting and regular key rotation to increase security.
Key endpoints: booking, status, reports
Booking endpoint: POST /api/v1/bookings — submit pickup address, destination, pickup window, parcel details and reference. The response returns booking_id and initial status. Status endpoint: GET /api/v1/bookings/{booking_id} — returns current status, driver info and ETA. Reporting endpoint: GET /api/v1/reports?from=...&to=... — generates daily/monthly summaries with delivery times and proof-of-delivery (POD) as PDF/JSON.
Data format and validation
The API uses JSON. Required fields include pickup and delivery address, parcel weight, dimensions and reference number. The API returns clear error codes (e.g. 400 for validation, 401 for auth). Validation prevents bookings with incomplete or unsafe shipment data.
Typical integration timeline and phases
Small integrations (webshop or CRM): 1–2 weeks. Mid-size integrations (ERP/WMS): 2–4 weeks. Larger projects with workflow changes or multiple systems: 4–8 weeks. Phases: field mapping, sandbox access, endpoint implementation, test runs, UAT and go-live.
Error handling and monitoring
Implement retry logic for transient 5xx errors. Log and alert for persistent failures. The API provides webhooks for status updates so your system can react in real time. Add a dashboard to track successful and failed bookings.
Frequently asked questions
What authentication does the API require?
You get an API key and use token-based authentication. All requests run over HTTPS. IP whitelisting is optional but recommended.
Can I make test bookings before going live?
Yes. A sandbox environment is available for test bookings, status simulation and validation without real pickups.
What data must my system supply?
At minimum: pickup and delivery address, parcel weight, dimensions and a reference number. Optional: recipient phone, service level (Sameday/Overnight) and special notes.
How do I receive proof of delivery?
Proof of delivery (POD) is available via the reporting endpoint as PDF or structured JSON. You can also receive POD via webhooks.