Step 5 - Response data

In v3 the response data has been changed. We will need to map the new response data.

info

The main difference to note is that all the flight and search data has been grouped into content.results

v1.0 (Before)

response
├── SessionKey
├── Status
├── Itineraries
├── Legs
├── Segments
├── Carriers
├── Agents
├── Places
└── Currencies

v3 (After)

response
├── sessionToken
└── content
    └── results
        ├── itineraries
        ├── legs
        ├── segments
        ├── places
        ├── carriers
        ├── agents
        └── alliances
    ├── stats
    └── sortingOptions

Let's explain what each of the main keys from the response is:

key	Description
sessionToken	Session token of the search
status	Status of the search is still running or completed
action	-
content	Contains flight data, stats and sorting conditions

Congratulations 👏, Thank you for migrating to v3 and following this guide. Now you've successfully migrated both endpoints.

You can now start showing your flight results

You can see an index on the changes to the response so you can map the fields correctly on the next page.