# EventAllocationsByEventId: Tixly Event Allocations by Event ID Fetches all allocations that are active on a specific event. ## Documentation Fetches all allocations that are active on a specific event. - Catalog: `Tixly` - Schema: `Event` - Label: Event Allocations by Event ID This is a read-only table function. The Tixly API may not support changing the data or the Invantive UniversalSQL driver for Tixly does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Tixly API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `EventAllocationsByEventId`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `id` | `` | ☑ | | EventId of the specific event | ## Columns of Table Function The columns of the table function `EventAllocationsByEventId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `Abbreviation` | `varchar2` | Abbreviation | ☐ | The abbreviation of the allocation type on the event | | `AllocationTypeId` | `int32` | | ☐ | The unique id of the allocation type | | `Block` | `char` | Block | ☐ | Is the allocation type blocked, meaning that they are excluded from the capacity of the event | | `CreatedUTCUnix` | `int64` | | ☐ | | | `Created` | `datetime` | Created | ☐ | | | `EventAllocationId` | `int32` | | ☐ | The unique id of the allocation type on the specific event | | `ExpiresHoursBefore` | `int32` | Expires Hours Before | ☐ | How many hours before the event does the allocation type expire | | `Id` | `int32` | ID | ☐ | The Id is the same as AllocationTypeId and is the unique id of the allocation type that was used, the name and expirations can be changed per event and therefore to be able to map the specific allocations to seats then use the EventAllocationId as that's unique per allocation and the event where it's used. | | `Name` | `varchar2` | Name | ☐ | The name of the allocation type on the event | | `ReservedTickets` | `int32` | Reserved Tickets | ☐ | Total number of seats reserved in the allocation | | `Seats` | `int32` | Seats | ☐ | Total number of seats that have the allocation | | `SoldTickets` | `int32` | Sold Tickets | ☐ | Total number of seats sold in the allocation |