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.
APIs and Data Exchange: Integrating Dispatch Tools with ERP & CRM
A practical guide for Swiss businesses: how to integrate dispatch tools with ERP and CRM using APIs. Authentication, sample JSON payloads and robust error handling.
Quick answer
You integrate dispatch tools with your ERP or CRM using standard APIs, OAuth2 or API‑key authentication, structured JSON payloads and reliable error handling. This automates order creation, tracking updates and status sync between systems like Abacus, SAP Business One, Microsoft Dynamics 365 or HubSpot.
When to integrate dispatch APIs
Integrate when you want to automate recurring orders, urgent same‑day runs or regular status updates. Integration reduces manual entry, avoids mistakes and speeds up delivery. Common Swiss use cases include spare‑parts delivery, urgent lab transfers and intra‑office document moves.
Authentication and security
Use robust authentication: OAuth2 for user contexts, API keys for server‑to‑server. Enforce TLS 1.2+ and rotate tokens regularly. Restrict API keys by IP and log access. For Swiss companies, consider data protection rules for personal shipment data.
Typical endpoints and payload examples
Key endpoints: /orders (create), /orders/{id} (status), /webhooks (subscribe) and /rates (cost/ETA). Sample order payload (JSON): {"orderReference":"INV-2026-001","pickup":{"address":"Bahnhofstrasse 1, 8001 Zürich","contact":{"name":"Anna Meier","phone":"+41 44 123 45 67"}},"delivery":{"address":"Industriestrasse 5, 4052 Basel","contact":{"name":"Marco Frei","phone":"+41 61 234 56 78"}},"parcel":{"weightKg":2.5,"dimensionsCm":{"l":30,"w":20,"h":10}},"service":"next_morning","notes":"Secure packaging, recipient signature"}.
Webhook vs polling strategy
Webhooks deliver real‑time events like accepted, picked_up, delivered or failed. Build endpoints that return 200 OK quickly and process events idempotently. For firewalled or legacy systems, use polling of /orders/{id}/status. Combine both: webhooks for instant updates, polling as a fallback.
Error and rate‑limit handling
Handle HTTP codes explicitly: 4xx for client errors (validate payloads locally), 5xx for server errors (retry with backoff). Implement exponential backoff, jitter and a dead‑letter queue for poison messages. Respect rate limits using Retry headers and adaptive throttling on 429 responses.
Testing, staging and go‑live
Use test keys and a staging API. Automate integration tests: order creation, status transitions, webhook replay and error cases. Run pilot deliveries in a controlled area — for example Zurich to Winterthur — before full rollout. Monitor API latency and error rates.
Frequently asked questions
What fields are required for a dispatch API order?
Minimum: pickup and delivery addresses, contact phone numbers, parcel details (weight, dimensions), service type and a reference ID. Optional fields include delivery window, return code and signature requirement.
How long does an integration take?
It depends on scope. A simple server‑to‑server flow can take days. Complex integrations with UIs, webhooks and monitoring typically take weeks.
What if webhooks don't arrive?
Check logs, firewall rules and replay features. Good providers retain events and retry. If not available, switch temporarily to polling.
Which monitoring metrics matter?
Useful metrics: API throughput, 4xx/5xx error rates, average latency, retry counts, webhook processing time and orders processed.