Sample (truncated) response excerpt (search returns itineraries, prices, properties such as SessionId, AgentId, GdsId, CombinationID and RecommendationID — use these in price confirmation):
Request example (use SessionId from PassengerDetails in confirm response):
Sample response:
Check Booking & Re-query
MyBooking API (GET):
https://api.staging.trips.ng/api/Flight/MyBookings?pnr=ZZZKJE&from=0&pageSize=10
Parameters: pnr, email, phone, from (default 0), pageSize (default 10).
Re-query / Check Booking Status API: https://api.staging.trips.ng/api/Flight/GetBookingStatus
Sample request:
Sample success response when found:
If booking not found:
Business reversal rules:
Reverse payment only when response is 200 OK and status = 0 or 1 or 11.
Reverse payment also when response is 400 Bad Request AND GetBookingStatus shows status = 0 or 1 or 11.
Status codes
0 — Booking
1 — Cancelled
2 — TicketIssued
3 — TicketPending
11 — CancellationFailed
100 — Error
International Flight (Round-Trip)
Use the same Search endpoint as One-Way. Example request includes two flight routes (outbound and return) and similar request body structure. ConfirmTicketPrice and ticketing flows are identical to One-Way but may include multiple FlightRoutes.
Confirm responses frequently return an array of confirmations (one per selected flight); each item includes NewPriceWhole and Hash — validate each using your MerchantKey and corresponding ConfirmationCode.
Response contains FlightRules, FlightRulePenalties and TermsAndConditions (some HTML content).
Road Transport (Bus) — Vendor Integration
Vendors receive a MerchantKey and MerchantCode. Authentication uses a bearer token which is SHA512(MerchantKey:MerchantCode). The API requires the following headers:
Authorization: Bearer {SHA512(MerchantKey:MerchantCode)}
(you can generate/test hashes at https://passwordsgenerator.net/sha512-hash-generator/ — do not change the URL)
MerchantKey: {merchantkey}
MerchantCode: {merchantcode}
Content-Type: application/json
BUS Search API: https://api.staging.trips.ng/api/Bus/SearchBus
Response includes HTML Terms and Conditions and textual rules.
Notes & Reminders
Always use the exact concatenation format: {MerchantKey}{ConfirmationCode}{NewPriceWhole} when computing the SHA-512 hash.
Do not share your MerchantKey. Hash validation occurs on your backend.
All URLs in this document must be used verbatim (do not modify query params or endpoints).
Many confirmation endpoints return arrays (especially domestic multi-leg or round-trip scenarios); validate the Hash for each returned confirmation entry independently.