> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/booking-engine-guide/changelog/changelog2025.md).

# Changelog 2025

## 31st October 2025

* Integrations: Added `reservationOwnerEmail` field to GTM purchase event in [Google Triggers Reference](https://docs.mews.com/booking-engine-guide/integrations/google-triggers-reference.md#purchase). This field provides the email address of the reservation owner and requires booking engine configuration to be enabled.

## 29th August 2025

* API: [Get services pricing](https://docs.mews.com/booking-engine-guide/booking-engine-api/operations/services.md#get-services-pricing)
  * Added `OccupancyData` request parameter.
  * Clarified the default behavior of `OccupancyPrices` property in [Category price](https://docs.mews.com/booking-engine-guide/booking-engine-api/operations/services.md#category-price) response object. Documentation-only, no change to the API.

## 16th July 2025

* API: [Get promoted services](https://docs.mews.com/booking-engine-guide/booking-engine-api/operations/services.md#get-promoted-services)
  * Added new operation (restricted).

## 10th February 2025

* API: Renamed and rewritten [Authentication](https://docs.mews.com/booking-engine-guide/booking-engine-api/guidelines/authentication.md) page, and other small changes. Documentation-only, no change to the API.

| Next                                                                                    |
| --------------------------------------------------------------------------------------- |
| [Changelog 2024](https://docs.mews.com/booking-engine-guide/changelog/changelog2024.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mews.com/booking-engine-guide/changelog/changelog2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
