Historical API

Provides shopping results based on general shopping request within designated time period from specific point (s) of sale. Allows to analyze prise fluctuations, off- peak and price jumps for specific destinations

Historical API request

Sample request (type: GET)

https://api.travelcloudpro.eu/v1/cache/history?searchPhrase=20170522IEVWAW&pointOfSale=UA&minSearchDate=2017-01-03&maxSearchDate=2017-01-10

Request parameters

The following table illustrates the minimum required data for cached shopping request.

Historical API response

Response example (application/json)

{
    "status": "success",
    "dataAvailable": true,
    "requestId": "42880234-0a5f-11e7-89f3-6b9a48544cdd",
    "executionTimeInMs": 244,
    "originalRequest": {
        "pointOfSale": "UA",
        "searchPhrase": "20170522IEVWAW",
        "minSearchDate": "2017-01-03",
        "maxSearchDate": "2017-01-10"
    },
    "data": {
        "proposalsCount": 1,
        "compressedDataSize": 2914,
        "uncompressedDataSize": 7341,
        "base64GzippedResponse": "H4sIAAAAAAAAA+2Xx67EyG6G3+VsNWPlNDvlnLMMw1ArZ7Wy+uK+u3suYK8MeG8cLUmCJdZfRdb37/...
    }
}

Upon decompression of base64GzippedResponse and JSON data display the user should be able to view object containing the following fields:

Direct

Shopping reponse contains the following elements:

  • Headers

  • Date

  • Proposals

Date

Date and time when data was transmitted to eStreaming API server.

Proposal

Each proposal represents shopping results containing a number of pricing options. A pricing option contains the following elements

Leg

A leg is basically a part of journey between two cities/airports, that can contain one segment in case of direct flights or multiple flight segments in case of connection or stopover.

Segments

Last updated