Release objects

Rate limits

This endpoint belongs to the priority lane.

Changes the object status to the previous selectable status. Usually, this means free. However objects that had status resale before go back to status resale when they get released.

Note

Releasing objects will make them available for selection again. Use this method with caution, as it can lead to double bookings in your system, if you release prematurely.

In most cases, a better alternative is to expire the hold token, which will automatically release the objects.

Text

POST https://api-{region}.seatsio.net/events/{eventKey}/actions/release

POST https://api-{region}.seatsio.net/events/{eventKey}/actions/release?expand=objects

PHP

$seatsioClient->events->release("event1", ["A-3", "A-5"]);

C#

await Client.Events.ReleaseAsync("event1", new [] { "A-3", "A-5" });

Java

client.events.release("event1", List.of("A-3", "A-5"));

Python

client.events.release("event1", ["A-3", "A-5"])

Ruby

seatsio.events.release('event1', ['A-3', 'A-5'])

Javascript

await client.events.release('eventKey', ['A-3', 'A-5']);

Go

result, err = client.Events.Release(event.Key, "A-3", "A-5")

Request

{
    "objects": ["A-3", "A-5"]
}

tip

This endpoint supports setting extraData when object format is used for objects. See Extra data for more information.

• objects: an array of object ID strings, or an array of objects with objectId and optional properties ticketType and extraData.
• holdToken: (optional): the hold token must be supplied when you want to make sure that the same person that made the hold releases the objects.
• keepExtraData: (optional): boolean. If set to true, the existing extra data doesn't get cleared
• channelKeys: (optional): an array of strings, i.e. the channel keys of the channel(s) to which the objects belong. If omitted, and the objects to be released are assigned to a channel, the request will fail with 400 Bad request. Pass in NO_CHANNEL as channel key to allow objects without a channel.
• ignoreChannels: (optional): if true, the release call succeeds, even if the released objects belong to a channel. Useful inside a back office application, in which the user is allowed to release any seat - no matter the channel. Should not be used in combination with channelKeys.

Response

Without expand=objects 204 - No Content

With expand=objects 200 - ok

{
  "objects": {
    "A-3": {
      "label": "A-3",
      "labels": {
        "own": {
          "label": "3",
          "type": "seat"
        },
        "parent": {
          "label": "Row A",
          "type": "row"
        },
      },
      "ids": {
        "own": "3",
        "parent": "A"
      },
      "status": "free",
      "categoryLabel": "Ground Floor",
      "categoryKey": "4",
      "ticketType": "adult",
      "orderId": "order1",
      "forSale": true,
      "objectType": "seat",
      "leftNeighbour": "A-2",
      "rightNeighbour": "A-4",
      "entrance": "Blue",
      "floor": {
        "name": "1",
        "displayName": "Ground Floor"
      }
    },
    "A-5": {
      "label": "A-5",
      "labels": {
        "own": {
          "label": "5",
          "type": "seat"
        },
        "parent": {
          "label": "Row A",
          "type": "row"
        },
      },
      "ids": {
        "own": "5",
        "parent": "A"
      },
      "status": "free",
      "categoryLabel": "Ground Floor",
      "categoryKey": "4",
      "ticketType": "adult",
      "orderId": "order1",
      "forSale": true,
      "objectType": "seat",
      "leftNeighbour": "A-4",
      "rightNeighbour": "A-6",
      "entrance": "Blue",
      "floor": {
        "name": "1",
        "displayName": "Ground Floor"
      }
    }
  }
}