Simulator
The simulator exists to make carrier integration testing simple.
It gives you a lightweight UI for checking how the carrier receives information from our system and, at the same time, for verifying how the Courier API endpoints behave during testing.
All simulator calls are made in the context of the Qest test carrier.
Authentication
When the simulator calls the YBOX Courier API, it authenticates with a Bearer token.
Token for Qest testing carrier is: 954e9f3bfb9357f2eb109afdc2cec182739150e6f5e0b19d546f62bcfa567044
What you see in the simulator
The simulator currently has four main routes:
| Route | Purpose |
|---|---|
/ | Dashboard with the main overview of the simulator |
/reservations | Reservation data sent through the simulator flow |
/boxes | Box-related data used in the carrier simulation |
/webhook-log | Incoming webhook events and payload history |
Why this simulator exists
The simulator is intended for first-level testing and onboarding:
- to see what information the carrier receives from Qest
- to inspect reservation and box data in one place
- to review webhook communication during test flows
- to validate how the Courier API endpoints work without using a real carrier environment
Typical use
If you are opening the simulator for the first time, think of it as a testing workspace for the Qest carrier integration.
You can use it to:
- trigger or review test scenarios
- inspect the data exposed to the carrier
- confirm that API calls and webhook deliveries behave as expected
For endpoint-level details, use the Courier API Swagger together with the simulator UI.