Booking CallBack

To help you stay updated with every flight booking status change, we offer a Callback URL feature. When a booking is marked as Pending, In Process, or On Hold, and its final status is determined (Success, Failed, or Aborted), our system will automatically send the updated response to your provided Callback URL. This response will include key booking details like PNR, Ticket Number, and Booking Status, so your system gets updated instantly without requiring manual intervention. You can configure or update your Callback URL anytime by logging into your dashboard. Navigate to the Settings > Callback URL section to manage it.
This feature ensures real-time synchronization between our booking engine and your system, enhancing automation and reducing delays.

Note 1 : This URL must be developed and maintained by your technical team and should be provided to us. This is not a URL from our system. We only send the data to this endpoint when the booking status changes.

Note 2 : For security purposes, we will send ClientId, UserName, and Password in every callback request. Please ensure that your system verifies these credentials before accepting and processing the data. If the credentials do not match, you should reject the request to prevent unauthorized updates.

Service URL (REST) to be used:
Request
Level Element Format Comments Mandatory
1 ClientId Integer Client ID is is your API client ID for verification purposes Mandatory
2 UserName String API Username is is your API username for verification purposes Mandatory
3 Password String API Password is is your API password for verification purposes Mandatory
4 EndUserIp String System IP Address of the End User Mandatory
5 TraceId String Unique identifier to track the request Mandatory
6 BookingId String Unique ID generated for the booking Mandatory
7 PNR String Booking Reference Number (issued by airline) Mandatory
8 GdsPNR String GDS System PNR (if available) Optional
9 Status String Final Booking Status:Shows booking result; for Failed or Aborted, the Remark field gives the reason and refund can be processed. Mandatory
10 Remark String Additional remark (e.g., Ticketed) Optional
11 Passengers Array List of Passenger Information Mandatory
11.1 Title String Passenger Title (e.g., Mr, Mrs) Mandatory
11.2 FirstName String Passenger First Name Mandatory
11.3 LastName String Passenger Last Name Mandatory
11.4 TicketNumber String Issued Ticket Number (if available) Optional
Response
Level Element Format Comments Mandatory
1 Error{} Object Error Mandatory
1.1 ErrorCode Integer Error Code 0 for success and 1 for failure Mandatory
1.2 ErrorMessage String Error Message if your system found any error then revert error message else keep it blank Mandatory