Check-in Workflow

This page describes how to perform passenger check-in using the GoNow API.

Authenticate

Obtain a session token from the Digital API token endpoint. This token is used for all GoNow requests. See the Get Started page for full authentication details.

curl --location "https://playground.api.tui/flight/newskies/rest/api/auth/v1/token/user" \
--header "Content-Type: application/json" \
--header "x-apikey: ${X_API_KEY}" \
--data "{
  \"credentials\": {
    \"username\": \"${NEWSKIES_USERNAME}\",
    \"password\": \"${NEWSKIES_PASSWORD}\",
    \"domain\": \"EXT\"
  }
}"

Store the token from the response for use in the Authorization: Bearer {token} header.

Perform Check-in

Once authenticated, perform the passenger check-in:

curl --location "https://playground.api.tui/flight/newskies/gonow/api/dcs/v1/checkin" \
--header "Authorization: Bearer ${TOKEN}" \
--header "x-apikey: ${X_API_KEY}" \
--header "Content-Type: application/json" \
--data '{
  "recordLocator": "{RecordLocator}",
  "segmentKeys": ["{SegmentKey}"],
  "passengers": [
    {
      "passengerAlternateKey": "{PassengerAlternateKey}"
    }
  ]
}'

Error Handling

The GoNow API may return HTTP 200 with an error payload in the response body. Always inspect the response for error objects:

{
  "errors": [
    {
      "code": "CheckinNotAllowed",
      "message": "Passenger cannot be checked in: travel document required."
    }
  ]
}

Common check-in error scenarios:

• Missing or expired travel documents
• Unmet security requirements (APIS/EES data)
• Flight already departed or closed for check-in
• Passenger already checked in on the segment