Error code
UNKNOWN
Unexpected error
On this page
Cause
A check without its own code failed (400, the message says which), or an unexpected error occurred (500). Examples of 400: "Journey 488213 is already in a final state", "Pickup date must be in the future". Some business rules still return 500, such as booking an add-on that is not on the quote or a pickup date in the past.
What to do
For 400, read message and correct the request. For 500, retry once; if it persists, contact Transferz support with the X-Request-ID you sent.
Endpoints that return it
- Suggest pickup time POST /quotes/suggest-pickup-time
The route could not be determined, for example because a location was not found.
- Search flights GET /flights/search
Neither arrivalDate nor departureDate is given.
- Resolve flight GET /flights/resolve
flightDesignator is empty.
- Unassign vehicle PUT /journeys/{id}/unassign-vehicle
The journey is completed or cancelled.
- Unassign driver PUT /journeys/{id}/unassign-driver
The journey is completed or cancelled.
- Update pickup information PUT /journeys/{id}/pickup-info
A pickup time was sent for a private journey, or the journey is not CONFIRMED, PLANNED or DRIVER_UNDERWAY.
- Assign vehicle PUT /journeys/{id}/assign-vehicle
The journey is completed or cancelled.
- Assign to driver PUT /journeys/{id}/assign-driver
The journey is completed or cancelled.
- Create action POST /actions
A type other than TRAVELLER_NO_SHOW or DRIVER_LEFT_PICKUP is sent (known issue).