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.
Digital integrations for SLA tracking
A practical guide for Swiss companies to add SLA tracking to ERP/TMS with APIs and webhooks — including status codes, payload examples and implementation tips.
Quick answer
You can integrate SLA tracking into your ERP or TMS using REST APIs and webhooks. Use a concise set of status codes (e.g. PICKED_UP, IN_TRANSIT, DELIVERED), subscribe to webhook events for real‑time updates, and add polling as a fallback. This puts SLA timestamps, exceptions and escalations directly in your systems.
Purpose of the integration
The goal is to feed SLA data automatically and reliably into your ERP or TMS. This enables automations for escalations, customer notifications and SLA reporting. For Swiss firms, it means clear delivery windows and documented SLA breaches.
Core components: API, webhook and polling
Use a REST API for queries and history lookups. Webhooks deliver real‑time state changes. Polling is the fallback when webhooks fail. Combine them: webhooks for normal flow, polling every 5–15 minutes during outages.
Recommended status codes and meaning
Keep a small, explicit set of statuses. Example: CREATED, ACCEPTED, PICKED_UP, IN_TRANSIT, ATTEMPTED_DELIVERY, DELIVERED, EXCEPTION, CANCELLED. Each status should include a timestamp and an optional reason for exceptions.
API examples and payloads
GET /shipments/{id} returns current status, planned SLA windows and event history. POST /shipments/{id}/events accepts status updates from carriers. Sample payload: {"status":"PICKED_UP","timestamp":"2026-09-07T09:12:00+02:00","location":{"lat":46.95,"lng":7.44}}. Validate timestamps as ISO‑8601 and use a consistent timezone.
Webhooks: design and security
Webhooks post events to your URL. Verify them with HMAC signatures or a shared secret. Acknowledge events with HTTP 200. Use header x‑x25pronto‑signature and make handlers idempotent to handle retries safely.
SLA rules and alerts
Define rules for SLA breaches, e.g. delivery after the agreed window or a single ATTEMPTED_DELIVERY without retry. Trigger automated emails, tickets or SMS from your TMS or ticketing tool. Record each escalation step for audit and billing.
Frequently asked questions
How often should I poll the API?
5–15 minutes is a common range. Use shorter intervals for mission‑critical shipments, but prefer webhooks for real time.
How do I make webhook handlers idempotent?
Save each event’s unique ID and ignore duplicates. Update states only if the incoming timestamp is newer or the event is new.
Which timestamp format should I use?
Use ISO‑8601 with timezone, e.g. 2026-09-07T09:12:00+02:00. UTC with Z is also fine. The key is consistency across systems.
How can I test webhooks during development?
Use tools like ngrok to expose local endpoints. Simulate webhook and API calls with Postman or curl. Check signature verification and retry logic.