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

# Upcoming changes

{% hint style="info" icon="telescope" %}
We're always working to improve Commerce Layer, so check this page regularly for updates and major releases info. You can also [browse the changelog](/changelog/readme.md) to see what's already shipped this year or [explore the archive](/changelog/archive/2025.md) for older history.
{% endhint %}

<p align="center"><a href="/pages/pzZ9URNE8mFwegeZQ9WQ" class="button primary" data-icon="calendar">Changelog</a><a href="/pages/DS4Y8uf2MOooHxQ8TajJ" class="button secondary" data-icon="box-archive">Archive</a></p>

***

{% updates format="full" %}
{% update date="2026-08-24" tags="core-api,breaking" %}

## Approximate record counts on large list requests

On [list endpoints](/core/pagination.md), `meta.record_count` and `meta.page_count` will become approximate once the matching result set exceeds 10,000 records — below that threshold, counts will stay exact as before. Check the new `meta.record_count_estimated` flag to know whether the counts you got back are exact or an estimate — when `true`, don't rely on them as precise totals. Page contents will stay exact either way.

{% hint style="success" %}
This also resolves intermittent timeouts previously seen on some high-volume list requests.
{% endhint %}
{% endupdate %}

{% update date="2026-09-15" tags="core-api,new-feature" %}

## Payments API redesign

A complete redesign of the payments part of our Core API is underway — decoupling payments from orders so authorizations, captures, and refunds can evolve independently, with native support for multiple transactions per order, first-class gift cards, richer wallet management, and agent-driven commerce flows. It's too big a change to summarize in a changelog entry, so read all about it [on our blog](https://commercelayer.io/blog/payment-api-redesigned).

{% hint style="info" icon="flask" %}
The version planned for release in mid-September will be a **beta**.
{% endhint %}

<details>

<summary><strong>Introducing our new Payments API. For humans and agents.</strong></summary>

A ground-up redesign of how payments work in Commerce Layer, built for both traditional checkout flows and agent-driven commerce.

<a href="https://commercelayer.io/blog/payment-api-redesigned" class="button primary" data-icon="book">Read more on our blog</a> <a href="https://commercelayer.fillout.com/t/n7qbQBzH63us?product=flex" class="button secondary" data-icon="user-headset">Contact sales</a>

</details>
{% endupdate %}

{% update date="2026-09-15" tags="core-api,breaking" %}

## Meta information consolidated at the document level

Completing the transition [announced earlier this year](/changelog/readme.md#document-level-meta-fields-in-api-responses) and shipping alongside the [Payments API redesign](#payments-api-redesign), the resource-level `meta` object will be reduced to a single field — `created_with_version`. The `mode`, `organization_id`, and `trace_id` keys will only be available at the document level from this release on.
{% endupdate %}
{% endupdates %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.commercelayer.io/changelog/upcoming.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.