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 pick-up data into ERP: API design and best practices
Concrete guide to import pick-up data into your ERP: auth, data fields, webhook patterns, error handling and Swiss use cases.
Quick answer
In short: build a clear REST API using JSON, protect it with OAuth2 or signed API keys, include standard fields for pick‑up address, time window and package details, and use webhooks for status updates. In Switzerland, exact time windows, ERP references and clear error logs are often essential.
Why a clean API matters
A well‑designed API reduces manual work, mistakes and delays. For Swiss SMEs with direct courier pickups this means faster processing, fewer phone calls and consistent ERP records. A clear order or billing reference in the API helps reconcile orders and invoices.
Recommended architecture
Use a REST API with JSON. Separate synchronous request/response flows (e.g. create pickup) from asynchronous events via webhooks (e.g. pickup confirmed, driver en route, delivered). Define rate limits and retry rules on both client and server sides.
Essential data fields for pickup orders
Reduce follow‑ups with consistent fields: - Client ID / ERP reference - Pickup address (street, postal code, city, canton) - Contact person, phone, email - Standardized time window (start, end, timezone CET) - Number of parcels, weight (kg), volume (m³) and max dimensions - Packaging type / special notes (e.g. fragile) - Billing code / cost centre - Optional: recipient address for pre‑delivery Validate inputs server‑side and return precise error messages.
Authentication and security
Protect the API with standard methods: - OAuth2 Client Credentials for system‑to‑system access or - HMAC‑signed API keys for simpler setups. Use TLS 1.2+ for transport. Implement roles and scopes so only authorized systems can create orders or receive status updates. Log access with request IDs for audits.
Webhook design and reliability
Webhooks deliver real‑time status. Practical tips: - Use standard events: created, confirmed, picked_up, in_transit, delivered, failed - Include a request ID and ERP reference in each event - Acknowledge receipt with HTTP 200 and a unique ack body - Implement retries with exponential backoff (e.g. 5s, 30s, 2min, 10min) and a dead‑letter queue for permanent failures - Provide a ping endpoint for integration tests
Error handling and monitoring
Good errors help developers. Use clear HTTP codes and structured error objects: - 4xx for client errors with field validations - 5xx for system errors including request ID Set up monitoring and alerts for failed webhooks, high latency or inconsistent status transitions. Surface logs in your ERP dashboard or SIEM.
Frequently asked questions
Which timezone should I use for pickup windows?
Use CET/CEST. Send time windows as ISO‑8601 timestamps with a clear start and end so ERP and courier systems stay aligned.
How do I avoid duplicate pickup orders?
Send a unique client reference or idempotency key with each request. The API should detect repeated keys and avoid creating duplicate actions.
What tests should I run before production?
Test authentication, full field validation, webhook reception under load, retry scenarios and end‑to‑end flows with realistic data. Also run access and security scans.
How do I handle sensitive contact data?
Only store necessary contact details. Encrypt personal data at rest and in transit. Follow Swiss data protection requirements that apply to your business.