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.
Sandbox testing and UAT: checklist for API go‑live
Step‑by‑step checklist for sandbox testing and user acceptance testing (UAT) before an API go‑live, aimed at Swiss businesses integrating courier services.
Quick answer
Before an API go‑live in Switzerland, run sandbox tests and UAT that cover functionality, security, performance and acceptance criteria. Test end‑to‑end flows, mask production data, measure load and recovery, exercise error scenarios and set measurable acceptance thresholds.
1. Plan: define scope and goals
Set the scope, success metrics and the endpoints to test. Identify business flows such as creating a shipment, scheduling pickup, querying status and canceling orders. Choose environments: developer sandbox, shared test sandbox and UAT with real users in Zurich, Basel or Geneva.
2. Test cases: functionality and E2E scenarios
Write test cases for normal and edge workflows. Examples: create order, update order, schedule pickup, poll shipment status, cancel. Validate input checks, authentication (API keys, OAuth) and correct HTTP status codes.
3. Data masking and test data
Use synthetic or masked production data. Remove or pseudonymize names, addresses and personal IDs to comply with DSGVO/DSG‑CH. Document datasets for repeatable tests and version your test data in the sandbox.
4. Performance and load tests
Simulate realistic peak loads: parallel order submissions, concurrent status queries and batch uploads. Measure latency, throughput and error rates. Test API scaling and timeout behavior under load.
5. Error scenarios and resilience
Simulate timeouts, network failures and malformed payloads. Verify retry logic, idempotency for repeated requests and transactional consistency. Ensure error messages and status codes help integrators troubleshoot quickly.
6. Security tests
Run authentication and authorization checks. Validate TLS, API key rotation, rate limiting and injection protections. Confirm no sensitive data is written to logs or returned in error messages.
Frequently asked questions
How do I mask production data correctly?
Replace personal fields with realistic pseudonyms or generate synthetic datasets. Remove identifiers, passwords and payment data. Keep masking rules documented and avoid storing raw dumps in test environments.
What acceptance criteria should I set?
Quantitative criteria: max response times, error rate below X%, successful execution of critical endpoints in Y% of tests. Qualitative: UAT sign‑off by key users and acceptable error handling. All critical bugs must be fixed or mitigated.
Who should join UAT?
Include the business owner, integration engineers, DevOps and a handful of operational key users. Add a support contact to collect and prioritise feedback during UAT.
How to test performance realistically?
Use load‑testing tools to reproduce real usage patterns: a mix of reads and writes, spike tests and endurance runs. Use data volumes and concurrency that match your peak business activity in the region.