---
title: "Getting started"
description: "Discover your API and prepare your first request."
url: "https://dev.kong-air.com/guides/getting-started"
image: "https://dev.kong-air.com/_og/d/c_Ocean.takumi,title_Getting+started,description_Discover+your+API+and+prepare+your+first+request.,props_eyJ0aGVtZSI6eyJjb2xvcnMiOnsicHJpbWFyeSI6IiMyQUJEQkIifX19,p_Ii9ndWlkZXMvZ2V0dGluZy1zdGFydGVkIg,s_gQcz7YT-hexnM-8G.png"
---

# Getting started

## [1\. Choose an API](#_1-choose-an-api)

Open the [API catalog](https://dev.kong-air.com/apis) and select the API you want to use. Read its OpenAPI contract for paths, parameters, request bodies, and response schemas.

| API                  | Gateway access                                               |
| :------------------- | :----------------------------------------------------------- |
| Flights              | Public; no API key or application registration required      |
| Destinations         | Public; no API key or application registration required      |
| Bookings             | Approved application registration and valid API key required |
| Customer Information | Approved application registration and valid API key required |

Portal sign-in controls documentation access; it does not automatically grant runtime access to a protected API.

## [2\. Confirm your environment](#_2-confirm-your-environment)

Check whether you are in the Development or Production Portal. Use the Gateway proxy URL for that environment, supplied by the platform operator. Do not use the Portal website URL as the Gateway URL.

Read [Environments and versions](https://dev.kong-air.com/guides/environments) before moving an integration between environments.

## [3\. Prepare a request](#_3-prepare-a-request)

For a public API, no credential is needed. With your Gateway URL set locally:

```bash
curl --fail-with-body "${GATEWAY_URL}/flights"
```

For a protected API, follow [Application access](https://dev.kong-air.com/guides/application-access) first. Review the selected contract before sending a request. Gateway authorization and the response returned by an upstream service are distinct: a service error does not by itself mean your application key was rejected.