General Errors
1 ) Could not fetch trip details. Trip is not available anymore. and
Seat is no longer available. Ans ) Please check, if you are caching data at your end for tripDetails() api. tripDetails will always be a live call.
2 ) Seat reserved for Males. Ans)
"Seat reserved for Males" ,
"Seat reserved for Ladies.Please select one of the seats reserved for gents: 11,3,UQ",
“Tentative Booking Failed / ERROR: Reservation could not be performed. Please check your parameters..5B are available for ladies, Please re-select the seat numbers 6E..”,
“Tentative Booking Failed / You Cannot Book Female Seat Near By Male Seat..”
To avoid these failures due to gender restrictions please implement below changes:
– We share "ladiesSeat": "true", when the seat is reserved for female passengers and "malesSeat": "true", when the seat is reserved for male passenger in tripdetails api response. When there is a gender restriction at Bus operator end, we are sending valid error messages in blockTicket api.
Such as :
– You can show pink color for a female reserved seat and also add message in UI ,
if male tries to book a female reserved seat or Female tries to book a male reserved seat. You can show message as below before calling blockTicket:
– Also, you can reduce these failures by consuming forcedSeats param in tripDetails API.
We are sharing forcedSeats property in tripDetails() response with '@' as the delimiter from which you have to take the first part as a female reserved seat and the second part as male reserved seats.
"forcedSeats": "femaleseat1,femaleseat2@maleseat1,maleseat2"
Sample Response:
{
"maxSeatsPerTicket": “6”,
“forcedSeats”: ”U11@”,
"seats": [
{
"available": "true",
"bankTrexAmt": "0.0",
"baseFare": "850.00",
"childFare": "0.0",
"column": "4",
For example "forcedSeats": "L4,L3@",
So, here L4 and L3 are female reserved seats. Now, vendor will not allow you to book any other seat for female passenger, if a forcedSeat is available. The forcesSeats needs to be filled first.
If a user tries to book any other seat, partner needs to display a message like "Please select one of the seats reserved for ladies: [L4, L3]" in UI.
With this implementation block will not fail and user can select the suggested seat. It will reduce your Tentative Booking failure.
3 ) Seat no longer available or invalid seat fare in booking request. Ans) This error occurs when incorrect fare sent in the block Request or the seat is not available.
Please check if there is a cache at your end for tripDetails() api. tripDetails should always be a live call. Also, check if the correct fare is sent.
Do not roundoff or add any amount in the fare value. Kindly pass fare in tripdetails api response as fare in blockTicket request.
"seats": [
{
"available": "true",
"bankTrexAmt": "0.0",
"baseFare": "1057.00",
"childFare": "0.0",
"column": "8",
"concession": "0.0",
"doubleBirth": "false",
"fare": "1109.85",
"ladiesSeat": "false",
"length": "2",
"levyFare": "0.0",
"malesSeat": "false",
"markupFareAbsolute": "0.00",
"markupFarePercentage": "0",
"name": "U10",
"operatorServiceChargeAbsolute": "0.00",
"operatorServiceChargePercent": "0",
"reservedForSocialDistancing": "false",
"row": "1",
"serviceTaxAbsolute": "52.85",
"serviceTaxPercentage": "5.0000",
4 ) Tentative Booking Failed / : REALTIME_UPDATE_FAILURE_IN_CONFIRM_BOOKING Ans) This error comes when the trip disabled or removed by the operator, so kindly check if you are caching tripDetails and availableTrips api data
5 ) Tentative Booking Failed / Journey is Canceled Ans) This error comes when the trip disabled or removed by the operator, so kindly check if you are caching tripDetails and availableTrips api data.
6 ) Invalid boarding point
Ans) This error will come when boardingpointid or droppingpointid passed in blockTicket request is incorrect. Please check, if the id is correctly passed, or if the data is cached at your end.
7 ) Tentative Booking Failed / AGE_CANNOT_BE_ZERO_IN_PAX_DETAILS
Ans) Age field should not be blank or zero , it's a Mandatory field. Please put a check at your end to enter this field in UI, so that block should not fail.
8 ) Tentative Booking Failed / Duplicate_Booking_Request
Ans) (Error from ias end due to duplicate request, need to investigate ).
9 ) Tentative Booking Failed / : IAS_TENTATIVE_BOOKING_FAILURE
Ans) This is a vendor side failure.
10 ) BLOCK_FAILURE: VENDOR_OMEGA_ERRORDESC_MISSING
Ans) ( vendor side error will need to investigate )
11 ) Could not block seat.
Ans) ( vendor side error will need to investigate )
12 ) Tentative Booking Failed / Fares got mismatched for 5ST
Ans) ( vendor side error will need to investigate )
Back to top
