Getting onto the Turkish Airlines developer platform takes three steps. You will need an account on this portal, an approved application, and the client credentials that application issues. Authentication is OpenID Connect — the same standard used across the Turkish Airlines estate.
Create your account
Register on the developer portal and sign in. Your account is the identity that owns every application and credential you create from here, and it is how the API team reaches you about version changes and deprecations.
Choose your APIs
Browse the catalog and select the APIs your integration needs, along with the service plan that matches your expected volume. Each plan carries its own rate limits, which are enforced at the gateway rather than in your code.
Register your application
Create an application, attach the APIs you selected, and submit it for approval. Once approved you receive an OpenID Connect client ID and secret — exchange those for a bearer token and start calling the APIs.
An API that is not documented is an API nobody can adopt. This guide covers how Turkish Airlines teams describe their services so that the specification itself — not a wiki page or a Slack thread — becomes the contract consumers build against.
Publishing puts your API in front of consumers — internal teams, travel partners, and third-party developers. This guide covers what has to be true before you publish, and what changes the moment you do.
Once an API is published, someone depends on it. Versioning is how Turkish Airlines evolves a service without breaking the integrations already in production — and how consumers know, ahead of time, what is about to change.