> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/november-2025-feature-wave/november-2025-feature-wave/november-2025-feature-wave-release-notes.md). # November 2025 Feature Wave: Release Notes Note: for a list of recent changes to Enate Marketplace integrations, see [this section](/whats-new/2024.1/2024.1-marketplace.md). *** #### Last updated 1st April 2026 **Bug Fixes** {% file src="/files/Bbu1RGFmgM1C3CVKwyiS" %} **Enhancements** {% file src="/files/k3uaDMRlKxgk71Ue9HB9" %} *** ## November 2025 Feature Wave Additional Documentation This is the production release for the November 2025 Feature Wave of Enate. It contains a number of new features, enhancements and bug fixes. ### Angular Version The November 2025 Feature supports Angular **Version 21**. **If you are using an advanced Enate Customer Card, please review the Angular versions your code relies on.**\ Your code is built on this framework, and compatibility issues may occur between releases. When Enate upgrades to a new **major** version of Angular, you should validate your code against the updated framework to ensure everything continues to work correctly. We will make every effort to notify you in advance if we are aware of any breaking changes. However, **code ownership and maintenance remain the responsibility of Enate customers. More info here -** ### Change Log The change log contains a detailed list of the new features, enhancements and bug fixes in this version of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below. ### Know Issues This is a downloadable copy of the known issues in this version of Enate. {% file src="/files/E2vLANAeNzJyyKNnYaL4" %} ### **API Changes** These are downloadable copies of the API changes in Enate's November 2025 Feature Wave release. They contain information about the API changes that have occurred between versions 2024.1 and the November 2025 Feature Wave of Enate. With the arrival of feature Waves, any new API will be named 'Version 1, then 2, then 3, etc'. Unchanged APIs still retain their older eg '2024.1' naming style. Supported API versions remain available across multiple Feature Waves, so adopting a new Feature Wave does not automatically require immediate API changes. However you should review these documents to identify new versions of APIs used in your integrations, which you will ultimately need to migrate to. See [**here**](/whats-new/feature-waves-an-overview.md#working-with-apis-and-feature-waves) for more information on working with APIs and Feature Waves. #### **Consuming APIs After the Version 1 API Release** With the introduction of the **Version 1 API**, the API surface has been reorganized to improve scalability and long-term maintainability. APIs are now grouped into three logical categories: * **Operational APIs (Work manager)** – APIs used for transactional and operational activities. * **Configuration APIs (Builder**)– APIs related to configuration, master data, and administrative setup. * **Legacy APIs** – A limited subset of APIs retained to allow customers to migrate gradually without immediate large-scale changes. #### **Migration Guidance** Prior to the Version 1 release, all APIs were consumed through a single endpoint. With the structure of Version 1, you will not need to migrate all integrations immediately as APIs that remain available in the legacy endpoint can continue to be consumed without change. If you are using the legacy API you will only need to carry out a base URL change. See below an example of the URL change required to consume legacy APIs: **Old URL: https\://{oldbaseurl}/webapi/{endpoint}** **New URL: https\:/{newbaseurl}/webapi/{endpoint}** It should be noted that Legacy APIs will be phased out in upcoming Feature Waves. APIs that are not available in Legacy must be consumed through the appropriate Version 1 endpoint, that is Operation or Configuration. In most cases, migration requires **only updating the base endpoint**, as request and response contracts remain unchanged unless otherwise documented. If you are using Version 1 Operation/Configuration APIs you will need to refer to the below change documents that contain the necessary authentication changes and API structure. The URL changes required for Version 1 operation and configuration APIs require you to add in either **/operational/** or **/configuration/** to your API URL. See the example below: **Operation: ** **Configuration: ** This phased migration approach enables you to move to Version 1 incrementally while maintaining continuity for existing integrations. #### Authentication Most endpoints In the API require you to pass an access token to allow the API to validate that the \ caller has the correct permissions to perform the requested action. To request an access token, you must use a UserApplicationCredential (these can be created In the \ Builder application). It Is not possible to create an access token with a standard Interactive username \ and password. For more information refer to the below API changes Documents. ### Other V1 API behaviour changes Some additional important changes in the V1 API versions and above: * Enum Parameters require Integer values rather than string values. The String to Integer mappings for this can be found [**here**](https://docs.enate.net/enate-help/integrations/enate-integrations/apis/api-enums). * Rate limiting controls how many request can be made in a short time period. * Payload validation rejects requests with data fields the API does not recognize or accept. For more information on these, see this section on [Key Behaviour changes in Feature Wave APIs](/whats-new/feature-waves-an-overview.md#key-api-behaviour-changes-for-v1-api-version-onwards). #### Version 1 Configuration API {% file src="/files/0vx0dv1JrOhu3FYyLprD" %} {% file src="/files/NFJlZdrlQIahm6Oz6pjm" %} #### Version 1 Operational API {% file src="/files/jBXqkn8eraJzCdNFrD59" %} {% file src="/files/vAuAHx9ivey8YNSemWRc" %} #### 2024.1 Legacy API {% file src="/files/L5SRAZZjV4at3K7897Lo" %} {% file src="/files/RncYEm7wnNjsFZ9XYu4o" %} ### Warehouse Database Data Dictionary This is a downloadable copy of the warehouse database data dictionary for all versions of the November 2025 Feature Wave of Enate. {% file src="/files/Zj0J9CRDIph2Mu6GXCtC" %} ### Breaking Changes Below is a copy of the breaking changes document for the November 2025 Feature Wave of Enate. It contains information about all the breaking changes within the Data Warehouse and Enate's APIs, and includes the validation codes for the November 2025 Feature Wave. {% file src="/files/ln0IwKOcaHNNxwI6LL8w" %} --- # 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://docs.enate.net/whats-new/november-2025-feature-wave/november-2025-feature-wave/november-2025-feature-wave-release-notes.md?ask= ``` 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.