Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hopper Authentication API

This API is authenticated with OAuth 2, Client Credentials grant.\Clients should use their `client_id` and `client_secret` to obtain an `access_token`.\The `access_token` should be included in every request, as a `Bearer` token on an `Authorization` header.\Note that `access_token`s eventually expire, requiring a new token to be fetched.see [authentication](#tag/Authentication)

Hopper Authentication API is one of 5 APIs that Hopper publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 6 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.

1 operations 1 paths 6 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1.1
Base URL
https://airlines-api.hopper.com/airline/v1.1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Hopper Authentication 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.

Authentication 1

This API is authenticated with OAuth 2, Client Credentials grant.\ Clients should use their clientid and clientsecret to obtain an accesstoken.\ The accesstoken should be included…

POST
/auth
Create an authentication token
postAuth body → 201400401403422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are auth_response (4 properties), error (3 properties), auth_request (2 properties), unprocessable_entity (1 property). Each schema is shown below with its type and property counts.

bad_request
object
1 property 1 required
unprocessable_entity
object
1 property 1 required
token_type
string
error
object
3 properties 1 required
auth_response
object
4 properties 4 required
auth_request
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hopper-com-authentication-api-openapi.yml Raw ↑

Other APIs Hopper publishes across the network.

Hopper Analytics API
Hopper Cancel For Any Reason (CFAR) API
Hopper Disruption Guarantee (DG) API
Hopper Sessions API