User Request Errors

Errors arrive as the GraphQL error message. <status>_user_request embeds the current status in lower case, for example confirmed_user_request.

Code	API	When
<status>_user_request	confirm, begin_personal_payment, decline, cancel, process, add_passenger_fee	The request is in the wrong status for this action
unauthorized	confirm, begin_personal_payment, decline, cancel, process	The caller can't act on this request — not its creator, or another admin is handling it
not_found	confirm, begin_personal_payment, decline, cancel, process, booking_request_progress	Unknown id, or no booking request yet
user_request_fee_not_found	confirm, add_passenger_fee	A fee id isn't one of the request's fees
duplicate_user_request_fee	confirm	The same fee id was sent twice
invalid_corporate_amount	confirm	A fee's corporate_amount is negative
corporate_amount_exceeds_price	confirm	A fee's corporate_amount is more than its price
no_personal_amount	begin_personal_payment	Nothing is left for the requester to pay
personal_payment_in_progress	begin_personal_payment	Another call started a payment at the same moment, and it ended before this call could return it; call again
fees_required	process	An update request was moved to ISSUED without fees
missing_fee_data	process, add_passenger_fee	A fee is missing the data matching its fee_type
fee_leg_required	process	A fee on a round-trip request has no leg
fee_leg_mismatch	process	A fee's leg isn't the request's leg
invalid_fee_leg	process	A fee's leg is ROUND_TRIP
invalid_fee_price	process	A fee's price is negative
duplicate_fee	process	Two seats, or two baggages, on the same leg
invalid_status	process	A PENDING request was sent straight to ISSUED
invalid_params	process	The request already has that status
locked_issued_request	process	Waiting for the requester to confirm or decline
locked_awaiting_personal_payment_request	process	Waiting for the requester to pay their part
locked_confirmed_request	process	Already confirmed; waiting for approvers
user_request_not_found	add_passenger_fee	Unknown user_request_id
user_request_fee_id_required	add_passenger_fee	user_request_id was sent without user_request_fee_id
paid_user_request_fee	add_passenger_fee	The fee was already applied
user_request_fee_type_mismatch	add_passenger_fee	fee_type isn't the fee's type
user_request_booking_mismatch	add_passenger_fee	The request is for a different booking
user_request_passenger_mismatch	add_passenger_fee	The request is for a different passenger
user_request_leg_mismatch	add_passenger_fee	The fee is for the other leg
payment_unreachable	add_passenger_fee	Payment service didn't answer; the charge may have gone through
id_or_user_request_id_required	booking_request_progress	Neither input field was sent
corporate_unauthorized	booking_request_progress	A non-admin who belongs to no company

Removed in this release: amount_required (now fees_required), consumed_user_request (now paid_user_request_fee), corporate_amount_required, corporate_amount_exceeds_amount and corporate_amount_not_allowed.

Each operation's own page lists the errors specific to it, under APIs. For authentication and role failures, see Middleware Errors.