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.
Integrating night transport APIs into ERP systems
Step‑by‑step technical guidance for IT and logistics teams to send night courier bookings from an ERP to a transport API. Covers data fields, auth, async events and testing.
Quick answer
You can automate night courier bookings from your ERP by implementing the right API endpoints, authentication, required data fields and workflows. Key data includes master records (customers, pickup and delivery addresses), shipment details (weight, dimensions, packaging), night pickup windows, pickup instructions, payment and internal references. Use token‑based auth, validate data in the ERP, accept asynchronous callbacks for status updates and add a retry policy for transient errors.
What the integration must do
The integration should create night courier bookings, return booking IDs, handle pickup confirmations and track status. It reduces manual effort and keeps a clear audit trail for accounting and operations in Swiss locations like Zurich or Geneva.
Required master data and shipment fields
Your ERP must provide: customer ID, sender and receiver address (postal code, city, country), contact name and phone, piece count, weight (kg), dimensions (L×W×H) or volume, packaging type, declared value, service code for night transport, requested pickup window (local time) and internal reference (order ID). Optional: delivery notes, signature required, billing party.
Authentication, security and access
Use token‑based auth (OAuth2 or API tokens) over HTTPS. Store credentials securely in an ERP vault or secret manager. Limit token scopes and rotate tokens periodically. Log requests without sensitive data such as payment details.
Endpoints, workflows and async events
Common endpoints: CreateBooking, GetBookingStatus, CancelBooking, GetPickupConfirmation and GetLabel/Document. Workflow example: ERP calls CreateBooking and receives a BookingID; the API later posts a webhook with pickup confirmation or status updates. Design the ERP to handle asynchronous events to avoid blocking processes.
Validation, mapping and error handling
Validate addresses and required fields before calling the API. Map local ERP fields to API fields (e.g. 'zip' → 'postal_code'). Implement retries for 5xx and network errors, and immediate operator alerts for 4xx validation errors. Keep an error log with API response codes and raw payloads for support.
Testing and go‑live checklist
Begin in a sandbox: 1) verify all mandatory fields, 2) test webhooks and replay scenarios, 3) check night pickup window conflicts for Swiss locations, 4) simulate cancellations and address updates, 5) measure latency and throughput. Move to production only after stable test runs.
Frequently asked questions
Which time format and timezone should I send?
Send ISO 8601 timestamps with local timezone (e.g. 2026-09-23T02:30:00+01:00). Local time accuracy matters for night pickups in Switzerland.
How do I avoid rejected bookings due to addresses?
Validate addresses in the ERP before sending. Check postal code and city combinations and include clear pickup notes. Log API errors and notify dispatch for manual correction.
How should I handle pricing and invoicing?
The API usually returns price references or billing IDs. Pass the billing_party field and store returned invoice references in the ERP for accounting reconciliation.
How can I secure webhook connections?
Use HTTPS with a valid certificate. Verify payloads via HMAC signatures or a shared secret. Make processing idempotent to handle duplicate webhook deliveries.