Skip to content
Korus Ticket API Specification
/
Form

KorusTicket API (1.0.4)

KorusTicket API documentation

Download OpenAPI description
openapi.json
openapi.yaml
Overview
URL

https://www.korusticket.com/

KorusTicket

[email protected]

License

None

Languages
Servers
Demo server

https://api.demo.korusticket.com/

Production server

https://api.korusticket.com/

BookingOrderDocument

The files associated to the Order. These are typically the customer's tickets for the Event.

Operations

BookingOrderItemTicket

A ticket is a single ticket for an OrderItem. A ticket is issued by the OrderItem's Order.

Operations

BookingOrder

An Order is an actual booking in the ticket issuer's system.

Operations

BookingReservation

A reservation temporarily holds an Offer, guaranteeing its availability and price for a limited time in the ticket issuer's system.

Operations

FormFieldChoice

Form field choice is a predefined option that users can select from a list of available values in a form field.

FormField

Form fields compose a form. A field has a type and can be required or not. When submitting a form, all required fields must be completed with valid values.

Form

A Form can be used to pass custom data to the API. A form is composed of FormField items.

Operations

Show a form

Request

Description

A form is used to collect additional data. For example, during the order process a form can collects essential customer information for the ticket issuer, including email addresses, allergy notifications, and required accommodations such as baby seats.

Attributes details

Code

The unique code of this form.

Fields

The fields composing the form. A field can of different types, and can be required or not.

Security
JWT
Path
idstring[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0...required

Form identifier

curl -i -X GET \
  'https://api.demo.korusticket.com/v1/forms/{id}' \
  -H 'Authorization: YOUR_API_KEY_HERE'

Responses

Form resource

Bodyapplication/ld+json
@contextstring or objectread-only
One of:
stringread-only
@idstringread-only
@typestringread-only
idstring
Example: "0195197f-7918-7285-bb4b-7df2b682c3eb"
codestring
Example: "customer_infos_form"
fieldsArray of objects(FormField.jsonld-v1.form.read)
Response
application/ld+json
{
  "@context": "string",
  "@id": "string",
  "@type": "string",
  "id": "0195197f-7918-7285-bb4b-7df2b682c3eb",
  "code": "customer_infos_form",
  "fields": [
    { … }
  ]
}

TicketingCatalog

A Catalog is the ticket issuer's collection of products and events. There is usually only one Catalog per TicketIssuer.

Operations

TicketingEvent

Event is an activity that can occur one or multiple times. Every occurrence of this event is a Session.

Operations

TicketingOfferAvailability

Ticket availability

Operations

TicketingOfferPrice

Offer Price

Operations

TicketingOfferTicket

The tickets contained in an Offer. A tickets give access to an Event's sessions.

Operations

TicketingOffer

It is the price table of a product. Offers defines the price and availability of a Product at a specific date.

Operations

TicketingProduct

Products are elements that can be purchased to access an Event. The price and availability of a product at specific date and for a specific category are specified in the Offer object.

Operations

TicketingSessionAvailability

Session availability

Operations

TicketingSession

Session is an occurrence of an event.

Operations