Scribd
Upload
8 views

Process and Flows

Uploaded by

tarekfouda0
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

Process and Flows

Uploaded by

tarekfouda0
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

References:

API: AER TiCKET API


BE: TreasureDeal Backend Server
FE: Client interface (website / mobile app)

Global Policies & Principles


- Access to service is only available for registered / logged in users
- Users’ information is validated from multiple sources (Payment methods, OTP codes,
verification emails, etc ...)
- Requests are constructed in FE, parsed and serialized, then sent to BE, which in turn
validates the request before sending it to API.
- Sensitive data and calculations are handled server side, never exposed to FE, only
delivered in static form.
- Request objects are safely typed and asserted through Classes and Interfaces
(typescript).
- A booking must be resolved within the current day, either ticketed / cancelled /
voided.

New Booking Flow:


1. Search available flights:
 Build search object (trip type, passengers, segments, search options)
 Send request to https://apihub-uat.aerticket-it.de/api/v1/search
 If there’s no results, repeat search with parameters dayIntervalPlus and
dayIntervalMinus

2. Select a result:
 Send request to https://apihub-uat.aerticket-it.de/api/v1/search-upsell and
display results if available

3. Select a fare:
 Send request to https://apihub-uat.aerticket-it.de/api/v1/verify-fare and
update prices
 Send request to https://apihub-uat.aerticket-it.de/api/v1/fare-rules and
display results
4. Data input required for booking:
 Passengers’ data
 Travel documents data
 Billing data

5. Create booking
 Display information input and fare rules from steps 2 and 4
 Send request to https://apihub-uat.aerticket-it.de/api/v1/create-booking

6. Get available ancillaries and seat maps:


 Send request to https://apihub-uat.aerticket-it.de/api/v1/available-booking-
ancillaries
 Send request to https://apihub-uat.aerticket-it.de/api/v1/available-seat-map
 Handle selection and create request object for both options

7. Booking process overview:


 View details for booking / ancillaries / seat map and await user consent
 If user canceled send request to https://apihub-uat.aerticket-it.de/api/v1/void-
booking

8. Process and validate user balance / payment

9. On success:
 Create booking ancillaries https://apihub-uat.aerticket-it.de/api/v1/create-
booking-ancillary
 Create booking seat reservation https://apihub-uat.aerticket-
it.de/api/v1/booking-seat-map
 Ticket booking https://apihub-uat.aerticket-it.de/api/v1/ticket-booking

10. Confirm operation:


 Check status from https://apihub-uat.aerticket-it.de/api/v1/retrieve-booking-
plus and notify user.
Cancel Ticketed Booking Flow:
1. Retrieve booking information from https://apihub-uat.aerticket-
it.de/api/v1/retrieve-booking-plus
2. Request cancellation and refund through customer service, through Cockpit portal /
email.

Re-Booking Flow:
1. Check if rebooking is possible through https://apihub-uat.aerticket-
it.de/api/v1/rebooking-search-info
2. on success request user input for booking segments (airports / time)
3. send request to https://apihub-uat.aerticket-it.de/api/v1/rebooking-search
4. verify possibility from https://apihub-uat.aerticket-it.de/api/v1/rebooking-verify
5. on success display new fare information
6. validate and process balance / payment method
7. consent from user
8. issue rebooking from https://apihub-uat.aerticket-it.de/api/v1/rebooking
9. check status using retrieve plus through https://apihub-uat.aerticket-
it.de/api/v1/retrieve-booking-plus and notify user.

You might also like