*Gap samples / Gap 11 - Release notes*

# Release notes: API v1 changes, autumn 2026

A sample entry for the Change Log, written from changes the API Reference already announces but the Change Log never recorded. Above it: the format, so every future entry answers the same three questions for the reader. Did anything change for me? Do I have to act? By when?

**Gap:** 11 of 13 · **Reader:** Admins and developers · **Type:** Release notes

## Why this page needs to exist

The help center's **Release notes** link opens the [Change Log](https://support.eulerapp.com/en/a/change-log), whose newest entry is dated 19 March 2026. Since then, EULER shipped or changed DealFlow AI, the EULER MCP connector, Forms 2.0 conditional logic and testing, Agreements V2 and API v1. Some of those changes need a customer to act, and the only place they are announced is inside the reference pages themselves.

The Change Log's one-line rows also say what changed, but not who is affected or what to do. That is fine for a fix. It fails for a change like the one below, where an integration's numbers move overnight.

## The format

- **Title:** what changed, in the reader's words.
- **Who it affects**, in one line. "Everyone" is rarely true.
- **Action required:** yes or no, first. If yes, what and by when.
- **Labels:** New, Changed, Deprecated, Fixed, as in [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). A breaking change is labelled even when it is small.

---

*Sample release notes start here*

## Referral list now includes older referrals

Changed  **Affects:** integrations that copy referrals from `GET /v1/referrals`.  **Action required:** yes, if you keep an incremental copy.

An internal filter was leaving out referrals whose submission type had never been recorded, which hid many older referrals. They are now returned. For the same query you will see a larger `total_count`, and an incremental sync will receive a one-off batch of older referrals it has not seen. Nothing was deleted and no field changed. The list now counts the same referrals as `total` on `GET /v1/analytics/referrals/funnel`, so the two reconcile.

**What to do:** let your sync insert the older rows rather than treating them as errors, and expect partner-sourced counts built on this endpoint to rise.

Date: September 2026, as stated in the API Reference. Exact day: [from engineering].

## Outbound forms now appear in the forms list

Changed  **Affects:** integrations that render `GET /v1/referrals/forms`.  **Action required:** only if you show the list to users.

The endpoint used to return only the forms you receive referrals on. It now also returns the forms you use to send referrals to a partner (`referral_type: "sent"`), which were not discoverable before. To keep the old behavior, add `?referral_type=received`.

Date: [from engineering].

## Referral direction is now read from the form

Deprecated  **Affects:** `POST /v1/referrals` callers.  **Action required:** no.

You no longer need to send `referral_type`. EULER reads the direction from `referral_form_id`. The field is still accepted, so existing integrations keep working, but a value that contradicts the form now returns `422`.

Date: [from engineering].

## Optional email notification when you create a referral

New  **Affects:** `POST /v1/referrals` callers.  **Action required:** no.

Set `send_email_notification` to `true` to email the receiving company's team about a new inbound referral. It defaults to `false`, which is how the endpoint has always behaved. It must be a JSON boolean: the string `"true"` returns `422`.

Date: [from engineering].

---

*Sample release notes end here*

## What wrong looks like

**WRONG - THE SAME CHANGE AS A CHANGE LOG ROW**

```
| 9/xx/26 | API | Fixed referral list filter |

Why it fails: it reads as a fix nobody needs to act on.
A RevOps team whose partner-sourced count jumps overnight
will open a ticket, or worse, report the jump upward.
The entry has to say who is affected and what to expect.
```

## Confirm with engineering

1. The four changes above shipped on [dates]. Correct me.
2. API changes go in the main Change Log, not a separate API changelog. Yes / no.
3. There is a changelog for the MCP connector at mcp.eulerapp.com/public/changelog that the help center should link to. Yes / no.

### Related documentation

- [EULER Change Log](https://support.eulerapp.com/en/a/change-log)
- [EULER API Reference](https://api.eulerapp.com/docs)
- [EULER MCP connector changelog](https://mcp.eulerapp.com/public/changelog)
- [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) (the labelling convention used here)

### Sources for this page

- API Reference: GET /v1/referrals ("Changed September 2026" notice), GET /v1/referrals/forms (outbound forms now included), POST /v1/referrals (referral\_type deprecated, send\_email\_notification).
- Change Log: newest entry 19 Mar 2026. Help center article dates for MCP setup (15 Oct 2026) and Forms 2.0 (4 Sep 2026).

### Next

- Gap 9: [Which EULER API to use](10-api.md). Start here if you are new to v1.
- Gap 12: [Style guide](13-styleguide.md). Including how release notes are labelled.

---

*Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*