> 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/upcoming-changes.md).

# Upcoming Changes

## Security Pack 2026Q4

During 2026Q4 and 2027Q1 we release a batch of breaking changes for security hardening. These changes reduce the risk of leaks of personal data and credit card data, and protect customers, guests and OTAs from attacks.

We release the changes during the next 3 months. You must adapt your integration within the next 6 months. The exact dates are in the Release Dates and Deadlines table at the end of this page.

### Upcoming Changes

#### Strict API Rate Limits

We introduce stricter API rate limits with the following configuration:

| Group                                              | Scope                | Per minute | Per hour | Per day |
| -------------------------------------------------- | -------------------- | ---------- | -------- | ------- |
| Standard endpoints (shared)                        | API key              | 600        | 18,000   | 216,000 |
| Standard endpoints (shared)                        | Organization account | 1,800      | 54,000   | 648,000 |
| One standard endpoint (route)                      | API key              | 300        | 3,600    | —       |
| One standard endpoint (route)                      | Organization account | 900        | 10,800   | —       |
| One booking and messaging endpoint                 | API key              | 100        | 3,600    | —       |
| One booking and messaging endpoint                 | Organization account | 300        | 10,800   | —       |
| Restrictions updates (`POST /api/v1/restrictions`) | One property         | 10         | —        | —       |
| Availability updates (`POST /api/v1/availability`) | One property         | 10         | —        | —       |

We introduce a limit for the whole Organization account and stricter limits for requests per API key.

Sensitive endpoints have stricter limits:

* `GET /api/v1/booking_revisions/feed`
* `GET /api/v1/booking_revisions`
* `GET /api/v1/bookings`
* `GET /api/v1/message_threads`
* `GET /api/v1/message_threads/:message_thread_id/messages`
* `GET /api/v1/bookings/:booking_id/messages`
* `POST /api/v1/bookings/:booking_id/messages/pull`
* `GET /api/v1/live_feed`

Most of our customers will not have any problems with these changes. During the next month, we will notify you if your application exceeds one of the new limits.

You should change your integration if it uses one of the following patterns:

* Calling `GET /api/v1/booking_revisions/feed` per property. Instead, call it once without `filter[property_id]`: one request returns the revisions of all properties that the API key has access to.
* Periodic polling of one of the following endpoints:
  * `GET /api/v1/message_threads`
  * `GET /api/v1/message_threads/:message_thread_id/messages`
  * `GET /api/v1/bookings/:booking_id/messages`
  * `GET /api/v1/live_feed`
* Periodic iteration over all pages of:
  * `GET /api/v1/booking_revisions`
  * `GET /api/v1/bookings`

If one of these patterns applies to your integration, review it and migrate to Webhooks.

From **16 November**, the new limits will work in detect mode.

From **14 December**, the new limits will work in block mode for all accounts.

#### Strict Entity Limits

To prevent problems caused by integration mistakes, we introduce entity 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) |
| `property_api_keys`                 | 2         | per property (active)             |
| `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                          |

For Vacation Rentals:

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

At the same time, we introduce validation rules that prevent duplicate entities:

* Taxes and tax sets must have unique titles.
* Cancellation policies must have unique titles.
* Webhooks must have unique target endpoints.

From **14 December**, entity limits will work in block mode for all accounts.

#### Remove Personal Customer Information from Email Notifications

To prevent leaks of personal data if a property mailbox is hacked, we remove the guest contact information (mail, phone, address, city, state, zip, country) from property booking notification emails.

This change will be released on **16 November 2026**.

#### Remove Personal Customer Information from the Booking API

From **16 November**, once a booking revision is acknowledged, we will mask (`***`) the guest contact information (mail, phone, address, city, state, zip, country, notes and raw\_message) from Booking and Booking Revision API responses. Then, even if an API key is stolen, attackers cannot get the contact information of guests from acknowledged bookings.

In the `customer` object, we will mask:

* mail
* phone
* address
* city
* state
* zip
* country

In the `booking` and `booking_revision` objects, we will mask:

* notes
* raw\_message

Each masked field will have the value `***`. The number of asterisks is fixed and does not depend on the length of the original value. If the original value is `null`, it stays `null`.

Example of masked message you can find at [Bookings Collection](https://docs.channex.io/api-v.1-documentation/bookings-collection.md#masked-booking-message) page.

Save the customer data on your side before you acknowledge the revision.

#### Strict TOTP-based MFA Authentication Flow

We will migrate from email second factor confirmation to TOTP-based second factor in two steps:

* From **14 December**, the TOTP-based second factor will be available. Each user can connect an Authentication Application.
* From **15 February** **2027** (two months later), the TOTP-based second factor will be mandatory. Each user must connect an Authentication Application and use it as a second factor to sign in and to get access to critical actions.

We will publish the list of critical actions later.

When you connect an Authentication Application, you get recovery codes. Keep them in a safe place. If you lose access to your Authentication Application, use a recovery code or contact our support team.

Trusted devices still skip the second factor at sign-in. This does not apply to the Organization Owner: the Organization Owner enters a TOTP code at every sign-in.

#### MFA Confirmation to Access Personal Customer Data in the UI

From **11 January, 2027**, to see the guest contact information (Phone, Email, Address) of a booking in our UI, you must confirm the access with a TOTP code from your Authentication Application. One confirmation gives access to one booking.

The same applies to credit card data: to see the card of a booking in our UI, you confirm the access with a TOTP code instead of an email code.

#### Remove Personal Customer Information from Embedded (IFrame) Mode

From **30 November**, we will stop showing the guest contact information (Phone, Email, Address) in the embedded (IFrame) mode, the same as in the other places above.

#### API Key Rotation Program

From **14 December**, we join the GitHub Secret Scanning Partner Program and release a new format of API keys. New API keys start with the `chx` prefix. Because of this, you must rotate all your API keys before **15 February, 2027**. After this date, we will revoke all old API keys.

If your API key is reported as leaked, we revoke it automatically and notify the Organization Owner. This helps to prevent API key leaks from source code.

Review your settings and repositories, and make sure that your source code does not contain API keys.

### Release Dates and Deadlines

Release: the date when the change starts to work. Deadline: the date by which your integration must be adapted. A dash means that no action is required from you.

| **Changes**                            | **Release**                              | **Deadline**                            |
| -------------------------------------- | ---------------------------------------- | --------------------------------------- |
| Strict API Rate Limits                 | <p>16 November 2026<br>(detect mode)</p> | <p>14 December 2026<br>(block mode)</p> |
| Strict Entity Limits                   | —                                        | <p>14 December 2026<br>(block mode)</p> |
| Remove PII from Emails                 | 16 November 2026                         | —                                       |
| Remove PII from the Booking API        | 16 November 2026                         | —                                       |
| TOTP-based MFA                         | 14 December 2026                         | 15 February 2027                        |
| MFA confirmation for PII in the UI     | 11 January 2027                          | —                                       |
| Remove PII from Embedded (IFrame) mode | 30 November 2026                         | —                                       |
| API Key rotation                       | 14 December 2026                         | 15 February 2027                        |
