How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TUI Group Token API

The token API from TUI Group — 13 operation(s) for token.

TUI Group Token API is one of 113 APIs that TUI Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Token. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 20 operations across 13 paths, and defines 72 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://prod.api.tui/flight/newskies/rest, https://playground.api.tui/flight/newskies/rest, https://prod.api.tui/flight/newskies/gonow, https://playground.api.tui/flight/newskies/gonow.

20 operations 13 paths 72 schemas 2 DELETE3 GET9 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://prod.api.tui/flight/newskies/rest
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

TUI Group Token API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (jwt) (JWT). By default, every request must be authenticated.

  • JWT — Paste your JWT token from the token endpoint.

Paths & Operations 20

Across 13 paths, the API surfaces 20 operations — 2 DELETE, 3 GET, 9 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

token 20
POST
/api/v1/tokendeprecated
Creates the general access token that will grant access to the API.
v1_token_post body → 201
PUT
/api/v1/tokendeprecated
Keeps the active token alive.
v1_token_put → 440200
DELETE
/api/v1/tokendeprecated
Abandons the active token.
v1_token_delete → 440200
GET
/api/auth/v1/token
Get the information about the short-lived JWT.
auth_v1_token_get → 200
PUT
/api/auth/v1/token
Updates the short-lived JWT.
auth_v1_token_put body → 201400401
GET
/api/nsk/v1/tokendeprecated
Get the information about the current token.
nsk_v1_token_get → 200
DELETE
/api/nsk/v1/tokendeprecated
Abandons the active token.
nsk_v1_token_delete → 200
POST
/api/nsk/v2/tokendeprecated
Creates the general access token that will grant access to the API.
nsk_v2_token_post body → 201202400
PUT
/api/nsk/v2/tokendeprecated
Given a non-null request, upgrades the current session's logged in user. Otherwise, keeps the active token alive.
nsk_v2_token_put body → 200201
POST
/api/auth/v1/token/anonymous
Create a short-lived anonymous JWT.
auth_v1_token_anonymous_post body → 201400
POST
/api/nsk/v1/token/culturedeprecated
Sets the culture code for the lifetime of the token.
nsk_v1_token_culture_post 1 param → 200
POST
/api/auth/v1/token/multifactor
Register multi-factor authentication options.
auth_v1_token_multifactor_post body → 201202400500
PUT
/api/auth/v1/token/role
Updates the short-lived JWT with new role permissions.
auth_v1_token_role_put body → 201400401
POST
/api/nsk/v1/token/serverTransferdeprecated
Transfers the server context from NewSkies and returns a new token.
nsk_v1_token_serverTransfer_post body → 201
POST
/api/nsk/v1/token/singleSignOn
Creates the general access token that will grant access to the API.
nsk_v1_token_singleSignOn_post body → 201
PUT
/api/nsk/v1/token/singleSignOn
Given a non-null request, upgrades the current session's logged-in user. Otherwise, keeps the active token alive.
nsk_v1_token_singleSignOn_put body → 200201
POST
/api/auth/v1/token/user
Creates a short-lived JWT specific to a user.
auth_v1_token_user_post body → 201202400500
PUT
/api/auth/v1/token/user
Updates an anonymous short-lived JWT to login as a user.
auth_v1_token_user_put body → 201202400
POST
/api/nsk/v1/token/user/person/singleSignOn
Creates a new user, links it with a provider, then logs in as the new user.
nsk_v1_token_user_person_singleSignOn_post body → 201
GET
/api/dcs/v1/token
Gets token-based information about the current user that is commonly used by DCS applications.
dcs_v1_token_get → 200401

Schemas 72

The contract defines 72 schemas that model the data the API accepts and returns. The most detailed are PersonCreateRequest (16 properties), JwtDetailsResponse (15 properties), PersonTravelDocumentRequest (14 properties), MultiFactorJwtResponse (11 properties). Each schema is shown below with its type and property counts.

PersonPhoneNumberRequest
object
Defines the the person phone number.
3 properties 2 required
MultiFactorType
integer
The Multi-Factor Authentication types allowed to authenticate with. 0 = Email 1 = ShortMessageService 2 = TimeBasedOneTimePassword
ServerTransferRequest
object
Represents a server transfer request.
4 properties 1 required
IJsonResponseOfString
object
Defines the JSON response contract.
3 properties
JwtRequest
object
Defines the nsk token request to gain access to the API.
4 properties 1 required
PersonPreferenceCreateRequest
object
Defines a person preference create request.
2 properties
SingleSignOnCredentials
object
Defines the single sign on credentials.
6 properties 2 required
JwtResponse
object
Represents the JWT response model.
10 properties
TokenResponse
object
Defines the token response.
2 properties
PersonStatus
integer
The status of the person. 0 = Active 1 = Terminated 2 = Suspended
PersonCustomerProgramCreateRequest
object
Defines a person's customer program create request.
6 properties 2 required
IJsonResponseOfJwtDetailsResponse
object
Defines the JSON response contract.
3 properties
PersonCommentRequest
object
Defines a person comment request.
2 properties
Exception
object
4 properties
PersonAliasRequest
object
Defines the person alias request.
6 properties
NskRoles
object
Defines the NSK role.
3 properties
JwtDetailsResponse
object
Represents the JWT details response model.
15 properties
JwtCredentials
object
Represents the base credential model.
6 properties 2 required
MessageStatus
integer
Defines the message status. 0 = General 1 = Warning 2 = Critical
SingleSignOnCreateRequest
object
Defines the single sign on create request.
3 properties 2 required
PersonCommentType
integer
Defines the different types of person comments. 0 = Default 1 = Itinerary 2 = Manifest 3 = Alert 4 = Archive 5 = Voucher
Gender
integer
Defines the different binary gender types. 0 = XX 1 = Male 2 = Female
JwtRefreshRequest
object
Defines the nsk token request to gain access to the API.
3 properties
NskTokenRequestv2
object
Defines the nsk token request to gain access to the API.
3 properties
MultiFactorRegisterResponse
object
Represents the register response model.
2 properties
UserIdentity
object
Defines the logged in users identity.
4 properties
IJsonResponseOfMultiFactorTokenResponse
object
Defines the JSON response contract.
3 properties
MultiFactorTokenResponse
object
Represents the JWT response model.
3 properties
MultiFactorRegistration
object
Represents the MFA registration model.
3 properties
IJsonResponseOfMultiFactorRegisterResponse
object
Defines the JSON response contract.
3 properties
PersonTravelDocumentRequest
object
Defines the person travel document.
14 properties 1 required
JwtImpersonateRequest
object
Defines the nsk token request to gain access to the API.
4 properties
Name
object
Defines a common name.
5 properties
PersonType
integer
Defines the type of person. 0 = None 1 = Customer 2 = Agent
NskServerContext
object
Defines the NSK server context.
6 properties
MultiFactorRegisterRequest
object
Represents the MFA response model.
3 properties 1 required
RoleBase
object
Defines the base role.
2 properties
IJsonResponseOfMultiFactorJwtResponse
object
Defines the JSON response contract.
3 properties
SessionPermissionType
integer
Defines the sessions permission type. 0 = Unknown 1 = Customer 2 = Anonymous 3 = Agent
NskSessionContext
object
Defines the nsk current session context.
9 properties
IJsonResponseOfTokenResponse
object
Defines the JSON response contract.
3 properties
EmailCreateRequest
object
Defines the person email create address.
3 properties 2 required
PersonAffiliation
object
Defines the person affiliation.
2 properties 1 required
RegisterCredentials
object
Represents the base credential model for registering.
4 properties 2 required
PhoneNumberType
integer
Defines the types of phone numbers. Note: New Skies does not support Mobile for booking contacts. 0 = Other 1 = Home 2 = Work 3 = Mobile 4 = Fax
PaymentMethodType
integer
Defines the payment method types. 0 = ExternalAccount 1 = PrePaid 2 = AgencyAccount 3 = CustomerAccount 4 = Voucher 5 = Loyalty
PersonStoredPaymentRequest
object
Defines the person's stored payment create request.
6 properties 3 required
PersonBasicInformation
object
Defines the person's basic information.
9 properties
ErrorResponse
object
Defines a unique error response.
8 properties
MultiFactorResponse
object
Represents the MFA response model.
4 properties
MultiFactorJwtResponse
object
Represents the MFA response model.
11 properties
IJsonResponseOfJwtResponse
object
Defines the JSON response contract.
3 properties
Message
object
Defines a unique informational message.
5 properties
NotificationPreference
integer
Describes types of notifications the user would prefer. 0 = None 1 = Promotional
IJsonResponseOfNskSessionContext
object
Defines the JSON response contract.
3 properties
PersonCreateRequest
object
Defines the person create request.
16 properties 1 required
UserCodes
object
Defines all the different user codes.
6 properties 4 required
ChannelType
integer
Defines the available channel types doing invoking the communication with the server. 0 = Default 1 = Direct 2 = Web 3 = Gds 4 = Api 5 = DigitalApi 6 = Digital…
SystemName
integer
Defines the system names. 0 = Default 1 = WinRez 2 = FareManager 3 = ScheduleManager 4 = WinManager 5 = ConsoleRez 6 = WebRez 7 = WebServicesApi 8 = WebService…
CredentialsBase
object
Represents the base credential model.
6 properties
MultiFactorRequest
object
Multifactor Request
3 properties
IJsonResponse
object
Defines the JSON response contract for a not content type response.
3 properties
TokenRequest
object
Defines the request to gain access to the API.
1 property
PersonAddressCreateRequest
object
Defines a person address request.
9 properties 1 required
PersonAliasType
integer
Defines the type of alternate name. 0 = Alias 1 = Variant
IJsonResponseOfDcsToken
object
3 properties
SessionPermissionType_2
integer
Defines the sessions permission type. 0 = Unknown 1 = Customer 2 = Anonymous 3 = Agent
MessageStatus_2
integer
0 = General 1 = Warning 2 = Critical
IJsonResponse_2
object
3 properties
DcsToken
object
10 properties
ErrorResponse_2
object
8 properties
Message_2
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tui-group-token-api-openapi.yml Raw ↑

Other APIs TUI Group publishes across the network.

TUI Group Account API
TUI Group Airline Profile API
TUI Group Air Shopping API
TUI Group APIS Message API
TUI Group Apo API
TUI Group Auth API
TUI Group Availability API
TUI Group Baggage API
TUI Group Bag Tag API
TUI Group Boarding API
TUI Group Boarding Devices API
TUI Group Booking/addons API
Where this information came from

This is an independent, third-party profile of TUI Group Token API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.