Test data on staging
How to get test journeys and bookings on staging, and how to trigger each scenario you need to test.
Staging behaves like production, but nobody drives the journeys. This guide shows how to create the data you need to test each part of your integration. You need a staging account and an API key.
Use fictional data
Staging is shared. Use made-up travellers with addresses at example.com and fictional phone
numbers, such as +44 20 7946 0123. Never use real traveller data on staging.
Transfer companies: get a test journey
Journeys reach you only when someone books them. The portal books them for you:
- Open Test data in the workspace.
- Choose a hub, an address and the direction.
- The portal books and pays a journey that is assigned to your company.
You receive journeyFleetAssignedEvent on your webhook endpoint,
and the journey appears in Search journeys. Use it to assign a
driver and a vehicle and to report progress.
Partners: run a journey
Your bookings on staging are not driven by a real transfer company. To see the events a real journey produces, use Send a test driver in the workspace: a simulated transfer company assigns a driver and a vehicle and moves the journey through its statuses, one stage at a time or automatically. Your endpoint receives the status, driver, vehicle and position events.
Hubs and routes
Quote requests need a hub as origin or destination. Not every hub has prices on staging.
Payments
Paying by invoice works on staging without extra data. Payment links and Stripe Connect need test cards.
Scenarios
| To test | How on staging |
|---|---|
| A new journey (transfer company) | Create a test journey in the workspace. |
| Driver and vehicle events (partner) | Book and pay, then send a test driver from the workspace. |
| A cancellation | Partners cancel their own booking. |
| A change | Partners change their own journey. |
| A webhook event of a given type | Transfer companies: Send a test event in the workspace webhook settings. |
| A forged webhook | Send your endpoint an event with a wrong signature yourself. |
| An error | Send a request with a missing required field, or a page size above 100. |