Hopper Sessions API
Hopper uses a unique ID to correlate API calls and events produced by a user's interaction with an airline application.The duration of the user's interactions is called a "session", and the correlation ID is called a `session_id`.A session begins immediately before the airline’s first API call to Hopper, and the airline must call the Create a Session endpoint at this time. A `session_id` is returned from this call; it must be included with each subsequent API call via the `HC-Session-ID` header. No airline action is required to end the session.
Hopper Sessions API is one of 5 APIs that Hopper publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 1 operation across 1 path, and defines 31 schemas. It is described by OpenAPI 3.0.3, at version v1.1.
Requests are made against a single base URL, https://airlines-api.hopper.com/airline/v1.1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Hopper Sessions API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (PartnerAuth).
An API key is passed in the header as HC-Session-ID (SessionAuth).
PartnerAuth— This API is authenticated with OAuth 2, Client Credentials grant.\ Clients should use their clientid and clientsecret to obtain an accesstoken.\ The accesstoke…SessionAuth— Header Parameters | headerName | description | |-----------------|---------------------------------------------------------------------------------------------…
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Hopper uses a unique ID to correlate API calls and events produced by a user's interaction with an airline application. The duration of the user's interactions is called a "sessio…
Schemas 31
The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are create_airline_session_request (7 properties), mobile (5 properties), tablet (5 properties), desktop (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Hopper 4
Other APIs Hopper publishes across the network.