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.
Follow the Book your first ticket tutorial for a step-by-step walkthrough that takes you from authentication through to downloading a ticket document.
Go through our API Reference 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
- fetch the catalog ID using the following endpoint: GET /v1/ticketing/catalogs
- fetch the product base ID using the following endpoint: GET /v1/ticketing/catalogs/{catalogId}/product-bases
- list all the product base's product using the following endpoint: GET /v1/ticketing/catalogs/{catalogId}/product-bases/{productBaseId}/products
- list product's offers: GET /v1/ticketing/catalogs/{catalogId}/offers?product={productId}
Our API supports only one method of authentication: OIDC
Refer to this page to authenticate.