Direct assignment
Proves your system receives a journey that Transferz assigns directly to your company, follows its changes and handles its unassignment, and that it reads the details correctly.
Instructions
- Set your webhook URL in the workspace first. The case can't start without it.
- Choose a hub, a direction (from the hub to the address, or from the address to the hub) and an address, and start the case. The portal creates a test journey on staging and assigns it directly to your transfer company. The later sections use the same hub and address.
- In every step the portal does something to the journey, waits until your endpoint answers the webhook event with a 2xx response, and then asks you one question about what your system received.
- Assignment: answer with the traveller detail the portal asks for.
- Pickup time: the portal moves the pickup a few minutes later. Enter the new pickup time (hours and minutes, local time at the pickup location).
- Driver comment: the portal adds a comment for the driver. Copy it from your system.
- Unassignment: the portal takes the journey away from your company again. Answer the event with a 2xx response.
- Each step waits up to 5 minutes for a 2xx answer. If Transferz delivers the event later and your endpoint answers it with a 2xx, the step still passes. Otherwise use Try again once your endpoint is fixed.
Pass criteria
- Your endpoint answers journeyFleetAssignedEvent, journeyExecutionDetailsUpdatedEvent, journeyTravellerInfoUpdatedEvent and journeyFleetUnassignedEvent with 2xx, each within 5 minutes (a 2xx to an event Transferz delivers late still counts)
- The traveller detail you enter matches the one in the assignment event
- The pickup time you enter matches the new pickup time
- The driver comment you enter matches the one the portal added
Links
- Guide:Receive journeys
- GET/journeys/{id}Get journey