# Test data on staging

> How to get test journeys and bookings on staging, and how to trigger each scenario you need to test.

Section: Essentials · Last updated: 2026-11-15

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:

1. Open **Test data** in the [workspace](https://developers.test.transferz.com/workspace).
2. Choose a hub, an address and the direction.
3. The portal books and pays a journey that is assigned to your company.

You receive [`journeyFleetAssignedEvent`](https://developers.test.transferz.com/reference/webhooks/journey-assigned) on your webhook endpoint,
and the journey appears in [Search journeys](https://developers.test.transferz.com/reference/transfer-companies/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](https://developers.test.transferz.com/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.

> **To be confirmed by Transferz:** The list of staging hubs and routes that return quotes is still to be confirmed by Transferz.

## Payments

Paying by invoice works on staging without extra data. Payment links and Stripe Connect need test
cards.

> **To be confirmed by Transferz:** The test cards for staging, and how to trigger a refused payment, are still to be confirmed by
> Transferz.

## 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.      |

## How long data stays

> **To be confirmed by Transferz:** How long staging keeps test journeys, bookings, webhook events and request logs is still to be
> confirmed by Transferz.

## Related

### Walk-through steps

- [Partner: get prices](https://developers.test.transferz.com/walkthrough/partner/get-prices)
- [Transfer company: receive a journey](https://developers.test.transferz.com/walkthrough/transfer-company/receive-a-journey)
