Introduction
API Description
| API | Description |
|---|---|
| shopping | Flight Search API, pairs with O/D city pair and date in RQ. Then gets all possible flight combinations results in RS. |
| pricing | Verify API, organizes the RQ with a specific flight option from Search RS. Then gets the latest accurate Price, Tax, and Availability for the specific flight. |
| booking | Booking API, calls this API with a specific flight option and passenger info details, contact information, FR24 would reserve the seat(s) for the user, and create a Booking for this transaction. NOTE: FR24 does not support user to cancel a booking by himself. If the user doesn’t take further action of Booking, then the order will be canceled by FR24 system automatically. That means, if the Booking status has not been changed to Ticketing Processing by user (triggered by Ticketing API calls or manual action on the portal), FR24’s system would cancel the order eventually. |
| ticketing | User should submit total price and booking number for the booking in the RQ to trigger ticketing process. Requesting the API of Ticketing successfully only means FR24 has received the ticketing application, and it will be pending rather than being instantly confirmed and issued. FR24 will notify the order status change via orderChangeInforming API if the booking is confirmed and the ticket can be issued. User could receive every booking’s and passenger’s e-ticket number by three methods below: 1. Developing an orderChangeInforming API with FR24’s method, which would receive pushing notification sent from FR24 with info including e-ticket number automatically and timely. 2. Calling orderDetail API in a 5-30 minute frequency, once ticket is issued successfully, FR24 would update info including e-ticket number into order Details. 3. Visiting b2b.flightroutes24.com website to check manually. |
| orderDetail | For API “orderDetail” and API “orderChangeInforming”, please at least choose one of them for integration. Order Details is another solution to get information in RS with e-ticket number, booking/order status, and all booking details. |
| orderChangeInforming | For API “orderDetail” and API“orderChangeInforming”, please at least choose one of them for integration. The API for getting order changed information, including e-ticket number, airline PNR, order status and schedule change. This API is a reverse workflow API, which user needs to develop a FR24’s method and provides a URL that allow FR24 update information to user. NOTE: Requesting the API of Ticketing successfully only means FR24 has received the ticketing application, and it will be pending rather than being instantly confirmed and issued. FR24 will notify the order status change via orderChangeInforming API if the booking is confirmed and the ticket can be issued. |
| presaleAncillaryShopping | Search for ancillary products that can be added and ordering with tickets. |
| postsaleAncillaryShopping | Search for ancillary products that can be added after the order being created. |
| ancillaryBooking | Create an ancillary order to reserve the ancillary products. |
| ancillaryPurchase | Post-sales ancillary order payment. |
| ancillaryOrderDetail | Get post-sales ancillary order details. |
| changeReshop | Search for available rescheduling flight |
| reissueRequest | Rescheduling confirmation |
| refundRequest | Refund Request Interface. By invoking the refundRequest interface, a refund pricing application will be initiated to FR24. The pricing result will be pushed through the orderChangeInforming API |
| refundConfirm | Confirmation of Refund Interface. By invoking the refundConfirm interface, FR24 will be notified to process the refund. It supports two scenarios: Call this interface to initiate a refund after pricing is completed.Support directly calling this interface to initiate a refund. |
| voidRequest | Ticket void request. |
Getting started
• The https API requests content-Type="application/json"
• API requests API URL and send the body that conforms to the JSON specification through "https post".
Create an application account
Header
| Name | Description |
|---|---|
| appkey | User account |
| Accept-Encoding | gzip |
| content-Type | application/json |
User authentication
Appkey and corresponding appSecret are assigned by FR24.
If partner requires the IP list of FR24, please contact FR24 business manager.
Production environment links
Modified at 2024-10-14 08:03:33