> For the complete documentation index, see [llms.txt](https://docs.veda.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veda.tech/api/change-log.md).

# Change Log

What's new, what's coming, and what's going away in the Veda API. New endpoints, breaking changes, and deprecations are announced here.

## Releases

### 2026-06 — Vaults & Trees

Three tenant-scoped endpoints for discovering vaults and inspecting the merkle roots and trees behind them.

**Available endpoints:**

* `GET /v1/vaults` — list the vaults that belong to your tenant — see [Vaults](/api/vaults.md)
* `GET /v1/vaults/{chain}/{vault_address}/roots` — list roots set on a vault (current and historical) — see [Vaults](/api/vaults.md)
* `GET /v1/trees/{root_hash}` — fetch a merkle tree by root hash (content-addressed, immutable cache) — see [Policy Manager & Merkle Trees](/api/policy-manager-and-merkle-trees.md)

These endpoints use a new standardized error envelope (`{ "error": { "code", "message", "details" } }`) and return `404` rather than `403` when a resource is outside your tenant, to avoid leaking existence. The Transaction Builder endpoints continue to use the legacy `{ "detail": ... }` shape until migrated separately.

### 2026-05 — Transaction Builder (public release)

The Transaction Builder API is now generally available to partner strategists.

**Available endpoints:**

* `GET /v1/tx-builder/api/actions/{chain}/{vault}/{strategist}` — list available actions
* `GET /v1/tx-builder/api/actions/{chain}/{vault}/{strategist}/constraints/{route}` — valid parameter combinations
* `POST /v1/tx-builder/api/execute/{chain}/{vault}/{strategist}/{route}` — build a single action
* `POST /v1/tx-builder/api/execute-multiple/{chain}/{vault}/{strategist}` — build an atomic batch

**Authentication:** Bearer tokens via API keys created in the [Veda Console](https://console.veda.tech).

See [Transaction Builder](/api/transaction-builder.md) for the full walkthrough.

## Deprecations

Deprecations will be announced here with a minimum **30-day** notice before removal. Deprecated fields and endpoints continue to work during that window, with a warning surfaced in the response.

* *No deprecations at this time.*

## Conventions

* **Dates** in this changelog are `YYYY-MM` for monthly groupings; specific releases use `YYYY-MM-DD`.
* **Breaking changes** are called out explicitly with the word "Breaking" and a migration note.
* **Additive changes** (new endpoints, new optional fields, new chains) are not considered breaking.