> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/upcoming-changes.md).

# Upcoming Changes

#### 15 September 2026

**🔔 Authentication Rate Limit**

A default rate limit of **40 requests per minute (RPM)** will be enforced on the authentication endpoints:

* `/login`
* `/login_check`

Most integrations operate well below this threshold and require no action. If your integration re-authenticates on every API request rather than reusing access tokens, adjust your auth flow before the enforcement date.

***

**🔔 Pagination Depth Limit (`_page` max 500)**

To prevent inefficient deep-pagination queries, a maximum value of **500** will be enforced for the `_page` parameter on the following endpoints:

* Custom events
* Members
* Member history
* Audit log
* Transactions
* Unit transfers
* Issue rewards (Redemptions)
* Collections

After 15 September 2026, requests with `_page` higher than 500 will return an error.

**How to retrieve data beyond page 500:**

* **Scroll Mechanism (recommended)** — The token-based `_scroll` API is designed for efficient bulk retrieval and has no page-depth limit. See [Scroll Mechanism for Pages](/technical-guide/api-fundamentals/scroll-mechanism-for-pages.md)
* **Data Exports** — For very large datasets and offline processing, use the platform's export functionality. See [Data Exports](/technical-guide/data-exports/overview.md)<br>

{% hint style="info" %}
Scroll is a separate mechanism from `_page` pagination and cannot be combined with it. For shallow queries (`_page` ≤ 500), existing pagination continues to work as before.
{% endhint %}

***

👉 For a full list of platform limits, see [Limits](/technical-guide/api-fundamentals/limits.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.openloyalty.io/technical-guide/upcoming-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.