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: automating direct courier orders from ERP systems
A practical guide for Swiss companies to connect their ERP with x25pronto. Covers technical prerequisites, required data fields, webhook handling and security best practices for automated pickups.
Quick answer
An API integration lets your ERP create x25pronto pickup orders automatically, receive status updates, and use webhooks for events. Key requirements are an API key, HTTPS, JSON payloads and secure authentication. Include sender/recipient, parcel dimensions, pickup time window, reference IDs and service type. Add idempotency, retry logic and secure webhook endpoints to ensure reliable automation in Zurich, Basel or Geneva.
Why integrate via API
A direct API cuts manual entry, reduces errors and speeds up order creation. Time‑sensitive shipments benefit because ERP triggers (order release or production finish) can instantly start a pickup with x25pronto.
Technical prerequisites
You need an x25pronto API key, servers that support HTTPS and JSON, and optionally IP whitelisting. Use TLS 1.2+ and modern cipher suites. Start in the sandbox environment before going live.
Required data fields and example payload
Core fields: sender (name, address, contact), recipient (name, address, contact), pickup_time_window (start/end), parcels (weight, length/width/height, quantity), reference_id (ERP order no.), service_type (direct courier), special_instructions. Example: {"sender":{...},"recipient":{...},"parcels":[{"weight":2.5}],"reference_id":"INV12345"}.
Webhooks for real‑time status
Use webhooks for events such as pickup_confirmed, in_transit, delivered and exception. Your ERP must accept POST requests with JSON. Validate each request using HMAC signatures or tokens. Persist status updates so business logic can react, for example releasing invoices after delivered.
Security and data protection
Limit personal data to what’s necessary and comply with Swiss DSG and applicable privacy rules. Use encrypted connections, role‑based API keys and rotate keys regularly. Keep access logs for audits.
Best practices for reliable automation
Design for idempotency using reference_id, handle retries for transient errors, use dead‑letter queues for failed messages, and monitor latency and error rates. Test edge cases such as address corrections or missing contacts.
Frequently asked questions
How do I avoid duplicate courier orders?
Send a unique reference_id from your ERP and check it on each request. The API supports idempotent calls so duplicate requests with the same reference_id will not create multiple orders.
What if a webhook delivery fails?
Implement retries and a polling fallback. Log failed deliveries and alert an administrator if your endpoint is down for a prolonged period.
Which fields are mandatory for a pickup?
Mandatory fields typically include sender address, recipient address, pickup time window, parcel weight/quantity and a reference ID. Phone numbers and special instructions speed up on‑site handling.
How can I test the integration without sending live pickups?
Use the x25pronto sandbox/test API. Simulate webhook events and test idempotency and error handling with test reference numbers.