# Getting started with Travelport TripServices

This guide links to the resources you need to get started using the TripServices APIs to develop your travel applications.

## Provisioning

Travelport provides the credentials required for the TripServices APIs at provisioning. You can then use the credentials access manager to create and manage those credentials.

If you aren't a current Travelport customer, send a Sales Inquiry form to learn more about our products.

## Authentication and Authorization

The TripServices APIs use OAuth 2.0 for authentication. You must send the credentials provided at provisioning to generate an authorization token to send in all subsequent API requests. A new auth token is required every 24 hours. See [Authentication](/docs/getting-started/authentication) for details and endpoints.

## Developer Toolkits

The developer toolkits for each API provide download files with supporting artifacts, including a Postman collection to view saved requests and responses and test your own data:

* [Flights API downloads](/resources/devkits-and-downloads#flights-api-devkits)
* [Stays API downloads](/resources/devkits-and-downloads#stays-api-devkits)
* [Pay API downloads](/resources/devkits-and-downloads#pay-api-devkits)


## Concepts and Terms

The guide topics for the APIs provide business usage details. The main guide for each API is the best starting point to learn about the terminology used in the travel industry and how that API works:

* [Flights API guide](/docs/flights)
* [Stays API guide](/docs/stays)
* [Pay API guide](/docs/pay)


Flights and Stays have several additional guides that cover separate functional areas of the API, such as search, booking, and ticketing for flights. Every guide has a Concepts and Terms section with relevant terminology for that area.

For flights, be sure to read the [Flights Search Guide](/docs/flights/guides/flights-search-guide). All linked TripServices API workflows start with the Search API, so you'll see the search concepts and example code patterns in that guide throughout the rest of the Flights API.

For a list of both travel terminology and terms specific to TripServices API concepts, see the glossary for each API.

## Endpoints and API References

While the Guides provide general usage information, every API has complete API references that provide all of the following in the same format:

* Reference tables detailing every object in the request and response
* Example request
* Example response


Each API also has a consolidated list of all endpoints and supported methods:

* [Flights API Endpoints](/docs/flights/general/flights-api-endpoints)
* [Stays API Endpoints](/docs/stays/general/stays-api-endpoints)
* [Pay API Endpoints](/docs/pay/general/pay-api-endpoints)


## Headers, Errors, Troubleshooting, and Support

Most other resources you need are on the General menu at the top of every page in this help, including:

* Common headers: The values every API request must pass in its header:
  * [Flights API Headers](/docs/flights/general/common-flights-api-headers)
  * [Stays API Headers](/docs/stays/general/common-stays-api-headers)
  * [Pay API Headers](/docs/pay/general/common-pay-api-headers)
* Error messaging: Error message formats and a list of error messages returned (not available for Pay):
  * [Flights API Errors](/docs/flights/general/error-messaging)
  * [Stays Errors](/docs/stays/general/stays-api-error-messaging)
* [Transaction and Trace IDs](/docs/flights/general/transaction-and-trace-ids): System-generated and custom values for tracking transactions in case you need to contact support.