Airline Ticketing & API Integration
Budget: $30 – $250 USD
I want to extend the ticketing module on wakkago.com so it handles the full life-cycle of an airline booking while talking directly to United Nigeria Airline and Xejet through their official APIs.
On the traveller side, the flow is simple: after a booking is confirmed, a user may later ask to cancel or to have the ticket re-issued if the airline changes the schedule. Every cancellation request should pause for my manual approval before any refund logic runs, while a reissue starts only when the traveller cites a schedule change.
For back-office staff, tickets must auto-issue the moment payment is confirmed, yet they must still be able to cancel or void them from the admin console when needed. All status updates returned by the two airline APIs have to stay perfectly in sync with the booking engine, including PNR, ticket number and fare rules.
Please plug the new endpoints into the existing Laravel/PHP stack (MySQL, Redis and Vue on the front end) and follow each airline’s doc for authentication, error handling and logging. Final code should be clean, commented and pushed to our Git repository with instructions so I can run a quick end-to-end test: book, pay, auto-issue, manual cancel, and schedule-change reissue.
On the traveller side, the flow is simple: after a booking is confirmed, a user may later ask to cancel or to have the ticket re-issued if the airline changes the schedule. Every cancellation request should pause for my manual approval before any refund logic runs, while a reissue starts only when the traveller cites a schedule change.
For back-office staff, tickets must auto-issue the moment payment is confirmed, yet they must still be able to cancel or void them from the admin console when needed. All status updates returned by the two airline APIs have to stay perfectly in sync with the booking engine, including PNR, ticket number and fare rules.
Please plug the new endpoints into the existing Laravel/PHP stack (MySQL, Redis and Vue on the front end) and follow each airline’s doc for authentication, error handling and logging. Final code should be clean, commented and pushed to our Git repository with instructions so I can run a quick end-to-end test: book, pay, auto-issue, manual cancel, and schedule-change reissue.