# Getting started

Korus Ticket API is organized around REST. It uses built-in HTTP features, like HTTP authentication and HTTP verbs, which are
understood by off-the-shelf HTTP clients. JSON is returned in all API responses, including errors.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail.

## 1. Discover our available endpoints

Go through our [API Reference](/openapi) to identify the endpoints you will need for your use cases.

Example: You need to list available offers for a specific product of a catalog

- you need to fetch the catalog ID using the following endpoint: [GET /v1/ticketing/catalogs](/openapi/ticketingcatalog/api_v1ticketingcatalogs_id_get)
- you will then list all the catalog's product using the following endpoint: [GET /v1/ticketing/catalogs/{catalogId}/products](/openapi/ticketingproduct/api_v1ticketingcatalogs_catalogidproducts_get_collection)
- finally, you will use the following endpoint in order to list product's offers: [GET /v1/ticketing/catalogs/{catalogId}/offers?product={productId}](/openapi/ticketingoffer/api_v1ticketingcatalogs_catalogidoffers_get_collection)


## 2. Authentication

Our API support only one method of authentication: OIDC

Refer to [this page](/authentication/oidc) in order to authenticate.