> For the complete documentation index, see [llms.txt](https://docs.channex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.channex.io/api-v.1-documentation/entity-limits.md).

# Entity Limits

{% hint style="warning" %}
**Planned limits.** From **14 December 2026**, entity limits will work in block mode for all accounts. Adapt your integration before this date. See [Upcoming Changes](https://docs.channex.io/upcoming-changes#strict-entity-limits) for the full list of changes in the Security Pack 2026Q4.
{% endhint %}

## Introduction

The Channex API limits how many entities of each type you can create, for example how many webhooks a property can have or how many API keys an Organization account can have. This page explains why the limits exist, what the limits are and what to do if your integration needs more.

## Why Entity Limits Exist

Most entity limits are far above what a correctly working integration needs. They exist to catch integration mistakes before the mistakes cause damage.

A typical mistake is a sync job that creates an entity on each run instead of updating the existing one. For example, a job that creates a new webhook each time it starts, or a new tax each time a property is saved. Without a limit, such a job can create hundreds or thousands of copies before anyone notices. This causes real problems:

* **Duplicate side effects.** Each duplicate webhook delivers the same event again, so your system receives and processes every booking several times. Duplicate taxes can be applied to the same price more than once.
* **Unclear data.** With many copies of the same policy or tax, it is unclear which one is the correct one, for you and for the property.
* **Slow responses.** Properties with too many entities take longer to load, sync and display, both in the API and in the UI.
* **Impact on other customers.** All customers share the same platform. A runaway integration uses resources that other properties need.
* **Security.** Limits on API keys and IP whitelist entries reduce the number of active credentials that can leak, and limit what an attacker with a stolen key can create.

With entity limits, a mistake like this stops at a known, small number of entities and the API returns an error that you can see and fix.

## How Entity Limits Work

Each limit applies to one entity type in one scope:

* **Per property** - the number of entities that belong to one property.
* **Per room type** - the number of entities that belong to one room type.
* **Per channel** - the number of entities that belong to one channel.
* **Per API key** - the number of entities that belong to one API key.
* **Per user** - the number of entities that one user creates.
* **Per Organization account** - the number of entities in the whole Organization account.

When an entity type is at its limit in a scope, the API rejects requests that create a new entity of this type in this scope. Requests that read, update or delete existing entities are not affected. To create a new entity, delete one that you do not use any more.

For API keys, only **active** keys count against the limit. Revoke the keys that you do not use.

## Limits

| Entity                              | Limit | Scope                                  |
| ----------------------------------- | ----- | -------------------------------------- |
| `groups`                            | 200   | Per user                               |
| `channels`                          | 50    | Per property                           |
| `webhooks`                          | 10    | Per property                           |
| `global_webhooks`                   | 50    | Per Organization account               |
| `taxes`                             | 20    | Per property                           |
| `tax_sets`                          | 10    | Per property                           |
| `hotel_policies`                    | 1     | Per property                           |
| `cancellation_policies`             | 10    | Per property                           |
| `channel_availability_rules`        | 50    | Per channel                            |
| `user_api_keys`                     | 20    | Per Organization account (active keys) |
| `property_api_keys`                 | 2     | Per property (active keys)             |
| `user_api_key_ip_whitelist_entries` | 20    | Per API key                            |
| `extras`                            | 200   | Per property                           |
| `extra_categories`                  | 50    | Per property                           |
| `room_type_spaces`                  | 10    | Per room type                          |
| `airbnb_performance_views`          | 20    | Per user                               |

### Vacation Rentals

For Vacation Rental properties, the limits for these entities are per room type:

| Entity                  | Per room type |
| ----------------------- | ------------- |
| `channels`              | 10            |
| `taxes`                 | 10            |
| `tax_sets`              | 2             |
| `cancellation_policies` | 10            |

For more information about property categories and room type limits, see [Property Size Limits](https://docs.channex.io/api-v.1-documentation/property-size-limits.md).

## Uniqueness Rules

Together with entity limits, the API validates that some entities are not duplicated:

* Taxes and tax sets must have unique titles.
* Cancellation policies must have unique titles.
* Webhooks must have unique target endpoints (`callback_url`).

A request that creates a duplicate entity returns a validation error. Find and update the existing entity instead.

## Increase a Limit

The limits fit almost all integrations. If your use case needs more entities than a limit allows, contact our support team at <support@channex.io>. We review requests case by case and can extend a limit for your use case.

In your request, include:

* The entity type and the limit that you need.
* The property, channel or Organization account the limit applies to.
* Why your integration needs more entities than the standard limit.
