General information

This section contains general information about the API.

Individual’s name title

We support the following name titles.

  • MR

  • MS

  • MISS

  • MRS

Supported ISO 639-1 language codes

  • da - Danish

  • de - German

  • en - English

  • es - Spanish

  • fi - Finnish

  • fr - French

  • it - Italian

  • no - Norwegian

  • pl - Polish

  • sv - Swedish

Supported ISO 4217 currency codes

  • DKK - Danish Krone

  • EUR - Euro

  • GBP - Pound Sterling

  • PLN - Zloty

  • SEK - Swedish Krona

  • USD - US Dollar

  • NOK - Norwegian Krone

Supported forms of payment

Payment card

  • MasterCard

  • Visa

  • Diners (only Diners issued from Nordic banks)

API rate limit

Our standard ratio is 100 request/second per client. This limit can be increased contacting support.

There is no Look To Book (L2B) limit.

HTTP compression

gzip

On the client side, you can advertise a list of compression schemes that will be sent along in an HTTP request. The Accept-Encoding header is used for negotiating content encoding.

Accept-Encoding: gzip

The server responds with the scheme used, indicated by the Content-Encoding response header:

Content-Encoding: gzip

Only gzip is supported as compression method.

Endpoints and protocols

All API access is over HTTPS, and accessed from the following URLs:

Development: https://services.norwegian.com.dev.nas.dev/retail
Production: https://services.prod.norwegian.com/retail

Timestamps

All timestamps are returned in ISO 8601 format:

YYYY-MM-DDTHH:MM:SSZ

Headers

The following headers should be sent with all requests.

Name Description

Authorization

Basic auth credentials.

Accept

The Accept header is used to specify media types which are acceptable for the response.

Content-Type

The Content-Type header is used to indicate the media type of the resource.

X-Correlation-Id

An id that is used for logging purposes.

Basic Authentication

Basic Authentication is used as an authentication scheme. The client must send HTTP requests with the Authorization header that contains the Basic word followed by space, and a base64-encoded string username:password. For example, to authorize as demo / p@55w0rd the client would send: Authorization: Basic ZGVtbzpwQDU1dzByZA==.

APIs

This describes the resources that make up the API. If you have any problems or requests please contact support.

Endpoints

GET

/

You can issue a GET request to the root endpoint to get all the endpoint categories that the API supports:

Request

HTTP Request
[show]

Response

HTTP Response
[show]

API overview

API Description

NDC - Shop and Order

This API will allow you to shop for flight products, price a shopping basket and then order.

Availability

Flight availability for flight origin/destination for a time period

Routes

Routes information

Code listings

Code listings

References

Postman collections and environments

Environment setup

Getting started collection