Prepare a repeatable test
Send your company name, integration contact, origin and destination countries, intended delivery services and expected requests per minute to your PacSort Online contact. Request a separate sandbox API key linked to the correct customer account and company, with status active.
Ask your contact to confirm the sender address, enabled distribution channels, carrier availability and pricing for the lanes you will test. A successful GET /health/auth confirms authentication; it does not prove that every delivery service is configured. Repeat this check with separately issued production credentials before going live.
Agree a repeatable sandbox test
Before POSTing, obtain an approved test recipient/address, sender configuration and enabled lane from your contact. Synthetic sample data is structurally illustrative; it is not a guaranteed deliverable address or a preconfigured carrier test case.
| Test | Expected check |
|---|---|
| Authentication | GET /health/auth returns 200 with status ok. |
| Approved booking | Save the assignment ID, poll to a label and verify its carrier, PDF and physical print. |
| Invalid input | Remove a required value in an agreed test case; check validation details and stop automatic retries. |
| Resume and reprint | Restart the integration with the saved ID; retrieve the existing label without another POST. |
| Delayed or uncertain response | Use a local mock to test polling timeout and lost POST responses without duplicating remote bookings. |
Confirm explicitly whether your sandbox setup contacts real carriers, sends notifications, schedules collection or creates charges. The environment name alone is not a guarantee that these effects are simulated. Agree test cleanup and release of buffered assignments before running the booking test.