Seating

High level example API flow for selecting or removing seats

Tip

Note

Request and response bodies are omitted from this example. Check the reference docs.

This functionality allows you to select or delete (remove) seats within an order.

Tip

If you select a seat for a passenger + segment that already has a seat selected then your new selection will replace the old one.

Seating takes 6-7 steps:

Tip

If you are just deleting seats then the first step can be skipped by basing the second step request (Quote) on details from order retrieve.

Check what seats are offered - GET /v1/servicing/seat/availability?supplierCode=BAE&supplierBookingReference=abcd
- Set the request URL parameters as appropriate
- NOTE request body has been omitted from this example
- Response will list all available seat maps for the order
Quote - Request a quote for selecting or deleting seats - POST /v1/servicing/seat/quote?supplierCode=BAE&supplierBookingReference=abcd
- Set the request URL parameters as appropriate
- NOTE request body has been omitted from this example
- The request body must specify the seats you wish to select per passenger per segment.
  - Passengers and segments are identified by their DID. To find the DIDs check the availability response or order retrieve response.
- If initially successful the response will then need polling
Poll for quote response - GET /v1/servicing/seat/quote/poll?asyncOperationToken=b3604d53-2e29-4d03-923d-565a98d7ad1e
- asyncOperationToken is from previous response
- Multiple polls may be required
Prepare - Provide payment details to get a final price - POST /v1/servicing/seat/prepare?transactionId=78dfe432-5159-490f-82ea-a63b90e77693
- NOTE request body has been omitted from this example
- transactionId is from the previous response
Poll for prepare response - GET /v1/servicing/seat/prepare/poll?asyncOperationToken=79c2b2e0-b982-4d27-8179-d03cbdd64142
- asyncOperationToken is from previous response
- Multiple polls may be required
Execute - Request seat selection/deletion be performed - POST /v1/servicing/seat/execute?transactionId=78dfe432-5159-490f-82ea-a63b90e77693
- NOTE request body has been omitted from this example
- expectedPriceAmount & expectedPriceAmountCurrency in request body must be correctly set based on totalPrice from previous response
  - This validates that you agree with PaxFaB Servicing’s calculations
- expectedPaymentAmount & expectedPaymentAmountCurrency in request body must be correctly set based on newPayment.totalAmount from previous response.
  - This validates that you agree with PaxFaB Servicing’s calculations
- Payment details must be provided in request. If these differ than at prepare undefined behaviour may occur.
Poll for execute response - GET /v1/servicing/seat/execute/poll?asyncOperationToken=0f2430a8-7500-416f-9877-923370f5ddb6
- asyncOperationToken is from previous response
- Multiple polls may be required