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 in practice: how hospitals and couriers connect their systems
Concrete examples for API endpoints, authentication methods, error handling and monitoring. For hospital IT and courier systems to automate bookings and track deliveries.
Quick answer
Hospitals and couriers connect systems with clear REST APIs using JSON, OAuth2 tokens, endpoints for orders and status, plus central error handling and monitoring. This automates bookings, enables near‑real‑time tracking and integrates logistics into hospital workflows.
Why integrate via API
An API links hospital IT with the courier system. It reduces manual entries and mistakes. Orders move automatically. Status updates arrive in near real time. Clinical staff get predictable, auditable handovers.
Common architecture and data flow
Both sides usually use a REST API with JSON. Hospital systems (LIS, ERP, exchange platforms) send booking requests to the courier API gateway. The courier responds with order ID, pickup window and driver info. Webhooks push status changes (picked up, en route, delivered). A message broker can help for high volume or retries.
Key API endpoints (examples)
1) POST /orders: Create an order with pickup address, recipient, package details and priority. 2) GET /orders/{id}: Order details with ETA and driver info. 3) PATCH /orders/{id}/status: Update status on pickup or delivery. 4) GET /shipments?date=YYYY‑MM‑DD: Day overview. 5) POST /webhooks/register: Register webhook endpoints for status events. These endpoints cover booking, tracking and feedback.
Authentication and permissions
OAuth2 with client credentials or JWT suits hospital integrations. Role and scope rules limit access. TLS (HTTPS) is mandatory. Token rotation, short lifetimes and IP allowlists improve security. Audit logs capture accesses for compliance.
Error handling and retry strategies
Use HTTP codes: 2xx success, 4xx client errors, 5xx server errors. Implement exponential backoff for 5xx errors. For 4xx, validate payloads and return clear errors (code, message, field). Make webhooks idempotent so duplicate events do not cause duplicate actions.
Monitoring, alerting and SLA tracking
Monitor API availability, latency and error rates. Tools like Prometheus, Grafana or cloud APMs work well. Alerts warn IT teams on rising 5xx rates or outages. SLA metrics (time‑to‑pickup, time‑to‑delivery) can be derived from status events and reported regularly.
Frequently asked questions
Which security measures should hospitals require?
TLS, OAuth2 or JWT for authentication, short token lifetimes, IP allowlists and audit logging. Also validate payloads and minimise personal data in requests.
How to register webhooks securely?
Register webhooks via an API endpoint with a confirmation challenge. Sign payloads (HMAC) and verify signatures server‑side. Restrict IP ranges and require HTTPS.
How to handle network outages for bookings?
Implement retry backoff and local queues in the hospital system. Log failed orders for later review and notify dispatch if critical.
What fields belong in an order payload?
Required: pickup address, pickup window, recipient address, package weight/size, priority and contact info. Optional: internal reference number and handover notes.