Digital Connect Check-In services are designed as a set of JSON services. Some of the services require a prior call to another Digital Connect Check-In service. This design significantly reduces application request processing time and API request model complexity. In this flow both services calls have access to shared business data which is stored on Digital Connect Check-In side and is referenced as Session Data.

Session Data

Session Data is identified by using a single HTTP header – Session-Id.

It is a unique alphanumeric identifier similar in format to UUID.

Session Lifecycle

The basics of Digital Connect Check-In session lifecycle are listed below:

• Sessions are created explicitly when a request is sent to POST /dcci/passenger/details service.
• Sessions are automatically removed after inactivity of 15 minutes.
• Executing any other service with the Session-Id resets the session expiration time.

Session Creation

To create a session, a request to POST /dcci/passenger/details service is required.

HTTP request

The following is the example of the request.

POST https://gateway/version/dcci/passenger/details?jipcc=<storefront>

The request headers should contain the following:

Content-Type: application/json 
Accept: */*
Accept-Encoding: gzip, deflate

HTTP response

The response contains the header that you can use to maintain the session. The HTTP headers are case-insensitive.

Session-Id: 0440a81aaae646f78c181d7491c246e6
Content-Encoding: gzip
Content-Type: application/json
Content-Length: 2125 
Date: Tue, 23 Sep 2019 15:33:11 GMT
{
"example": true
}

Session Use

To execute a request within the scope of an existing Session, HTTP header Session-Id has to be present in the request.

HTTP request

The following is the example of the request.

POST https://gateway/version/dcci/passenger/checkin?jipcc=<storefront>

The request headers should contain the following:

Content-Type: application/json
Accept: */*
Accept-Encoding: gzip, deflate
Session-Id: 0440a81aaae646f78c181d7491c246e6

HTTP response

The response includes the Session-Id provided in the request.

Session-Id: 0440a81aaae646f78c181d7491c246e6
Content-Encoding: gzip
Content-Type: application/json
Content-Length: 2125
Date: Tue, 23 Sep 2019 15:33:11 GMT