Adding Extra Bags

This guide will go through the changes you need to make in the booking flow to be able to list and book services for any offer you want. It's important you know the basics of how to create a booking.

• If you are not familiar with how to create an order please heads over to our Quick Start Guide.

• This guide will start from an offer so make sure you grab an offer ID for a British Airways flight before we start.

Baggages are a type of what we call available_services. Available services are specific to an offer but not surfaced through the API by default. The changes we'll make to work with available services are:

• Retrieve an offer along with its available_services

• Include services to order creation

• See the services booked on an order

We start by fetching the offer to make sure to get its most up to date information. The get offer endpoint gives you the ability to retrieve available services with the offer by applying the query param return_available_services set to true. Using a valid offer id you can use:

Curl
1
curl -X GET --compressed "https://api.duffel.com/air/offers/<ID>?return_available_services=true" \
2
  -H "Accept-Encoding: gzip" \
3
  -H "Accept: application/json" \
4
  -H "Duffel-Version: beta" \
5
  -H "Authorization: Bearer example_token"
6

This request will return an offer which now include the available_services attribute.

Available services

The only available service currently supported is baggages. Wi-fi and meals are a couple of the options we aim to support in the near future. Each available service is unique and identifiable by id. The price of the service is described by total_currency and total_amount. And the actual service information is determined by its type and metadata.

Important to notice that services are specific to segments and passengers. The relationship is described by the attributes segment_ids and passenger_ids.

Learn more

For a complete description of the available services schema checkout the API reference.

• https://duffel.com/docs/api/offers/schema

Once you know what offer and service a user wants to book all you have to send request to the create order endpoint with 2 small changes to the payload.

Curl
1
curl -X POST --compressed "https://api.duffel.com/air/orders" \
2
  -H "Accept-Encoding: gzip" \
3
  -H "Accept: application/json" \
4
  -H "Content-Type: application/json" \
5
  -H "Duffel-Version: beta" \
6
  -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" \
7
  -d '{
8
  "data": {
9
    "selected_offers": [ "off_001" ]
10
    "payments": [ ... ],
11
    "passengers": [ ... ],
12
    "services": [
13
      {
14
        "quantity": 2,
15
        "id": "ser_00001"
16
      },
17
      {
18
        "quantity": 1,
19
        "id": "ser_00002"
20
      }
21
    ]
22
  }
23
}'
24

You must add the attribute services to your request payload. This field should contain a list of services to be book along with the offer specified in the selected_offers field. Each service on the list here must contain the available service id and the desired quantity.

The payment amount must be increased by the amount times quantity of each service you'd like to purchase. For example, if your offer total is 50 GBP and you include service A with quantity 2 and total_amount 10 GBP, the amount of the payment should now be 70 GBP.

Once the booking has gone through in the airline's system we will return the usual order create response payload to you. You can always retrieve your order by id:

Curl
1
curl -X GET --compressed "https://api.duffel.com/air/orders/<ID>" \
2
  -H "Accept-Encoding: gzip" \
3
  -H "Accept: application/json" \
4
  -H "Duffel-Version: beta" \
5
  -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>"
6

Services

The service object will look exactly the same as the available service expect for maximum_quantity being replaced with quantity. It's worth flagging that any ancillary baggages booked as services will not be present in the slices[].segments[].passengers[].baggages[]. They are only present in the services field. If you want the full picture of a passenger's baggage you will need to combine both.

Documents

Some airlines record the booking and the payment of ancillary services in a document different from the electronic ticket issued for the flight. These documents are called Electronic Miscellaneous Documents. When available we expose them in the API as a document with a type of electronic_miscellaneous_document_associated.

Learn more

For look at the services and documents schema, please visit our API reference:

• https://duffel.com/docs/api/offers/schema

Now you are able to include baggages to an order! Once we support more ancillary services you'll be able to rely on the same flow but apply it to other available service types. If you'd like to get a deeper look into the API reference to learn more you can jump to:

• Offer Available Service Schema

• Order Service Schema

• Create Order Endpoint

If you still haven't learned how to cancel an order we recommend looking at that next:

• Cancelling an Order