Current Version

By default, all requests will receive the v1 of the API. We encourage you to explicitly request this version via the Accept header.

Versions

Currently there exists one version of the Norwegian Availability API: the v1 version.

By default, all requests receive the v1 version. We encourage you to explicitly request this version via the Accept header.

Media Types

Custom media types are used in the API to let consumers choose the format of the data they wish to receive. This is done by adding one or more of the following types to the Accept header when you make a request. Media types are specific to resources, allowing them to change independently and support formats that other resources don’t.

All Norwegian Availability media types look like this:

application/vnd.nas.availability[.version].param[+json]

The most basic media types the API supports are:

application/json
application/vnd.nas.availability.v1+json
Important
 the default version of the API may change in the future. If you’re building an application and care about the stability of the API, be sure to request a specific version in the Accept header as shown in the examples below.

You can specify a version like so:

application/vnd.nas.availability.v1+json

You can check the current version through every response’s contentType header:

HTTP Response
[show]

Calendar Availability

GET

/availability/calendar

Flight availability for flight origin/ destination for a time period.

Request

HTTP Request
[show]
Table 1. Routes
Name Type Required Default Description

departureAirportCode

String

Yes

None

Departure (origin) airport code. Use a three letter location identifier assigned according to the IATA Resolution 763

arrivalAirportCode

String

Yes

None

Arrival (destination) airport code. Use a three letter location identifier assigned according to the IATA Resolution 763

startDate

String

Yes

None

Starting Date of the stay period range. Example: 2017-01-13

endDate

String

Yes

None

Ending Date of the stay period range. Example: 2016-03-13

travelerQuantity

String

Yes

None

Number of travelers

Response

HTTP Response
[show]
Table 2. DateAvailability
Name Type Required Default Description

originDestinations

Array

Yes

None

Flight origin/ destination information

originDestinations[].departure.airportCode

String

Yes

None

Departure (origin) airport code

originDestinations[].arrival.airportCode

String

Yes

None

Arrival (destination) airport code

originDestinations[].departureDates

Array

Yes

None

Scheduled departure date