---
title: "EventAllocationsByEventId (Tixly)"
description: "Event Allocations by Event ID"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/tixly/Tixly.Event.EventAllocationsByEventId
original: https://documentation.invantive.eu/en/datamodels/tixly/Tixly.Event.EventAllocationsByEventId
updated: 2026-11-01T16:24:42Z
license: https://documentation.invantive.eu/en/
---

# EventAllocationsByEventId: Tixly Event Allocations by Event ID

`read only` `REST`

- Catalog: `Tixly`
- Schema: `Event`
- Label: Event Allocations by Event ID

Fetches all allocations that are active on a specific event.

Can only retrieve data.

## Summary

Fetches all allocations that are active on a specific event.

## API Source

- Endpoint: `/events/{id}/allocations`
- Operation: `get /events/{id}/allocations`

## Parameters

| Name | Data Type | Required | Default | Documentation |
|---|---|:---:|---|---|
| `id` | `` | [x] |  | EventId of the specific event |

## Table Columns

The columns of the table `EventAllocationsByEventId` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `Abbreviation` | `varchar2` | Abbreviation | [ ] | filters on the platform, writable, `Abbreviation` | The abbreviation of the allocation type on the event |
| `AllocationTypeId` | `int32` | itgen_tixly_allocationtypeid | [ ] | filters on the platform, writable, `AllocationTypeId` | The unique id of the allocation type |
| `Block` | `char` | Block | [ ] | filters on the platform, writable, `Block` | Is the allocation type blocked, meaning that they are excluded from the capacity of the event |
| `Created` | `datetime` | Created | [ ] | filters on the platform, writable, `Created` |  |
| `CreatedUTCUnix` | `int64` | itgen_tixly_createdutcunix | [ ] | filters on the platform, writable, `CreatedUTCUnix` |  |
| `EventAllocationId` | `int32` | itgen_tixly_eventallocationid | [ ] | filters on the platform, writable, `EventAllocationId` | The unique id of the allocation type on the specific event |
| `ExpiresHoursBefore` | `int32` | Expires Hours Before | [ ] | filters on the platform, writable, `ExpiresHoursBefore` | How many hours before the event does the allocation type expire |
| `Id` | `int32` | ID | [ ] | filters on the platform, writable, `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 | [ ] | filters on the platform, writable, `Name` | The name of the allocation type on the event |
| `ReservedTickets` | `int32` | Reserved Tickets | [ ] | filters on the platform, writable, `ReservedTickets` | Total number of seats reserved in the allocation |
| `Seats` | `int32` | Seats | [ ] | filters on the platform, writable, `Seats` | Total number of seats that have the allocation |
| `SoldTickets` | `int32` | Sold Tickets | [ ] | filters on the platform, writable, `SoldTickets` | Total number of seats sold in the allocation |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Tixly](/en/release-notes/drivers?driver=tixly)

