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 handover logs: API connection to courier bookings
Link digital handover logs automatically to x25pronto courier bookings via API. Technical requirements, field mapping and example request flows included.
Quick answer
You link handover logs automatically by sending a PDF or structured JSON to x25pronto with the booking_id after delivery. Required items include an API key, booking reference, checksum and metadata like sender/recipient. Below you find field mapping, sample requests and common error handling.
Why link digital handover logs to courier bookings?
Automatic handover logs reduce paperwork and errors. For Swiss firms in retail, manufacturing or IT, this means faster traceability, reliable archives and clear audit trails. Use the x25pronto booking ID as the primary key between booking and handover.
Technical prerequisites
You need an x25pronto API key, HTTPS-capable servers and a system that generates handover logs as PDF or structured JSON. The API requires TLS 1.2+, proper Content-Type headers and unique booking references (e.g. booking_id). Optionally use webhooks to receive push notifications when a booking completes.
Field mapping: required and optional fields
Required fields: booking_id, timestamp, signer_name, signer_role, signature_type (e.g. manual, e-sign), document_checksum (SHA256). Optional fields: pickup_address, delivery_address, package_count, comment, gps_coordinates. For PDF uploads send metadata as JSON and the file as multipart/form-data; for structured logs send JSON with an attachments array.
Sample API workflow (push model)
1) Your app creates or receives the handover log after delivery. 2) POST /v1/bookings/{booking_id}/handover with Authorization: Bearer {API_KEY}. 3) Body: metadata JSON + file (handover.pdf) as multipart or application/json with items array. 4) x25pronto replies 200 and returns a handover_id. 5) Optionally, a webhook notifies your system upon confirmation.
Example request (JSON)
POST /v1/bookings/12345/handover Headers: Authorization, Content-Type: application/json Body: {"booking_id":"12345","timestamp":"2026-09-07T10:15:00+02:00","signer_name":"John Meier","signature_type":"manual","document_checksum":"e3b0c...","items":[{"id":"1","description":"Sample parcel","count":1}]} Response: {"status":"accepted","handover_id":"h-67890"}.
Error handling and best practices
Validate checksums before upload. Check HTTP codes: 400 for missing fields, 401 for auth issues, 409 for existing handover. Use idempotent requests: include a handover_id or document_checksum to prevent duplicates. Log request/response pairs locally for audits. Test in a sandbox before going to production.
Frequently asked questions
Which file formats are supported?
PDF is recommended. Structured JSON is an alternative for systems that exchange data without a file. When sending attachments use multipart/form-data.
How do I ensure the log matches the booking?
Send the booking_id and a document checksum (SHA256). x25pronto links both and returns a handover_id. Also include address or package_count in metadata for extra verification.
Can I use webhooks for status updates?
Yes. Register a secure HTTPS URL in the partner portal. Webhooks notify you when a handover is accepted or rejected.
Are there limits on file size or upload volume?
Limits usually apply. Test in sandbox mode. For large volumes or big files, coordinate with the x25pronto integration team for options.