> 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/april-2026-feature-wave/april-2026-feature-wave/april-2026-feature-wave-release-notes.md).

# April 2026 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 18th June 2026

**Bug Fixes**

{% file src="/files/RgNcedFRJB2rSbXi4oVJ" %}

**Enhancements**

{% file src="/files/7QjHpsz2bYG1wkKbHysw" %}

### API Changes

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.

Some important changes in the V1 API versions:

* Enum Parameters require their Integer values rather than String value. 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). 

{% file src="/files/jNIVdQtmTswp9ZCRsSiD" %}

{% file src="/files/72wDMVuSePVpW44cSlWK" %}

### Validation Codes

{% file src="/files/556K4PJagdZXYE9Sio7R" %}

{% file src="/files/4DJym85MCy0t6OCGuMCf" %}

### Know Issues

{% file src="/files/JaQS94m6cZUyEnvODg2I" %}


---

# 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.enate.net/whats-new/april-2026-feature-wave/april-2026-feature-wave/april-2026-feature-wave-release-notes.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.