Creates a new order with the specified tickets and / or items

This endpoint creates orders containing the specified tickets and / or items. The licence requirements vary based upon the contents supplied for the order.

Example Request - Tickets / Ticket Packages Only

{
  "ticketTypes": [
    {
      "showtimeId": "817E5232-A130-4FEB-4306-08D4718A775F",
      "id": "0001",
      "quantity": 2
    }
  ]
}

Example Request - Items Only

{
  "items": [
    {
      "id": "44a9e030-e13a-e911-b8b3-000d3aa05a0a",
      "quantity": 1,
      "modifiers": [
        {
            "id": "46a9e030-e13a-e911-b8b3-000d3aa05a0a",
            "quantity": 1
        }
      ]
    }
  ]
}

Example Request - Tickets / Ticket Packages and Items

{
  "ticketTypes": [
    {
      "showtimeId": "817E5232-A130-4FEB-4306-08D4718A775F",
      "id": "0001",
      "quantity": 2
    }
  ],
  "items": [
    {
      "id": "44a9e030-e13a-e911-b8b3-000d3aa05a0a",
      "quantity": 1,
      "modifiers": [
        {
            "id": "46a9e030-e13a-e911-b8b3-000d3aa05a0a",
            "quantity": 1
        }
      ]
    }
  ]
}

For Orders Containing Tickets

When creating an order or adding ticket(s) to an order, if there are insufficient seats available in a contiguous block in a row the seats will not be automatically allocated. When this occurs the seatsRequireSelection response property is set to true and the seats must be explicitly selected by the customer before completing the order. Refer to Get Screen Layout for Order and Update Selected Seats for details on how to do this. If you do not wish to support seat selection within your application, then contact us to configure the MX Transactional API to prevent orders from being created that must have the customer select their seats from being created. In this case the API will instead respond with the following error code: 41002 - The selected seats could not be automatically allocated in a single row, and the customer will need to select another showtime to purchase tickets for.

Ticket packages are added to orders in exactly the same way as normal ticket types.

For Orders Containing Only Items

Some cinema chains support the creation of orders that contain only items (i.e. no tickets are contained in the order). Where this is the case, the cinema chain will have itemsOnlyOrdersEnabled set to true in Get Cinema Chains.

Order Expiration Time

If expirationTimeUtc is present in a response to any of the ticketing requests, then it specifies the expiration date and time for the order (in UTC). Population of this field is only supported by a subset of cinema chains (for example, for cinemas chains running Vista Connect it requires Connect v4.5.8 or later) – if this field is omitted then the order’s expiration date is unknown and the consuming application should use a default assumption of a fixed expiration period from the point of creating the order.

📘

License Requirements

For orders containing Only Tickets and / or Ticket Packages - MX Tickets
For orders containing Only Items - MX Items
For orders containing Tickets and Items - MX Tickets and MX Items

Language
Authentication