Last updated:
03-Aug-2026
Recent changes:
Merge branch 'feature/NSK-76937' into 'master'
update api product values
Closes NSK-76937
See merge request api-program/apigee/flight/newskies-apis/boardingpass!124
Description
Overview
The NewSkies Boardingpass API provides check-in and boarding pass services for TUI airlines. It is an Apigee X-fronted API backed by an AWS Lambda service that integrates with Navitaire NewSkies for passenger and booking data.
Authentication
The API uses OAuth 2.0 Bearer tokens. Obtain an access token using client credentials flow and include it in the Authorization header.
Authorization: Bearer <access_token>Required Headers
| Header | Required | Description | Example |
|---|---|---|---|
Authorization |
Yes | OAuth 2.0 Bearer token | Bearer eyJhbGci... |
X-SourceMarket |
Yes | Source market identifier (determines airline-specific configuration) | uk, de, nl, be |
Base URLs
| Environment | Base URL |
|---|---|
| Development | https://dev.api.tui/flight-newskies-boardingpass/ |
| Test (SIT) | https://test.api.tui/flight-newskies-boardingpass/ |
| Pre-Production | https://preprod.api.tui/flight-newskies-boardingpass/ |
| Production | https://prod.api.tui/flight-newskies-boardingpass/ |
Quick Example
curl -X POST "https://test.api.tui/flight-newskies-boardingpass/bookings/ABC123/boardingpasses?lastname=Smith&outboundDate=20260815" \
-H "Authorization: Bearer <access_token>" \
-H "X-SourceMarket: uk"Endpoint Categories
Booking Operations
| Method | Path | Description |
|---|---|---|
| POST | /bookings/{bookingId}/boardingpasses |
Get boarding passes for a booking |
| POST | /bookings/{bookingId}/barcode |
Generate barcode for a specific passenger/segment |
| POST | /bookings/{bookingId}/pdf |
Generate PDF boarding pass |
| POST | /bookings/{bookingId}/pkpass |
Generate Apple Wallet pass |
| POST | /bookings/{bookingId}/googlePayPass |
Generate Google Pay pass |
| POST | /bookings/{bookingId}/email |
Email boarding pass to recipients |
| GET | /bookings/{bookingId}/checkinstatus |
Get check-in status for a booking |
Settings & Configuration
| Method | Path | Description |
|---|---|---|
| GET | /settings/availability/{origin}/{destination}/{airline}/{date} |
Check if online check-in is available |
| POST | /settings/autodoccheck/{origin}/{destination}/{airline} |
Check auto document requirements |
| POST | /settings/webcheckin/{origin}/{destination}/{airline}/{date} |
Check web check-in eligibility |
| GET | /settings/checkinconfig/{carrierCode} |
Get check-in configuration rules |
| GET | /settings/generalsettings |
Get general settings |
System
| Method | Path | Description |
|---|---|---|
| POST | /system/ping |
Health check endpoint |
Response Codes
| Code | Description |
|---|---|
| 200 | Success |
| 201 | Created (Google Pay pass) |
| 400 | Bad Request — invalid parameters or business rule violation |
| 401 | Unauthorized — invalid or expired token |
| 403 | Forbidden — insufficient permissions |
| 404 | Not Found — booking or resource not found |
| 429 | Too Many Requests — rate limit exceeded (spike arrest) |
| 500 | Internal Server Error |
Rate Limiting
The API enforces spike arrest policies to protect backend services. If you receive a 429 response, implement exponential backoff before retrying.
Email operations are additionally protected by a quota policy to prevent abuse.
