---
title: "Get Pending Tree"
method: GET
path: "/trees/{root_hash}/pending"
tags: ["Trees"]
---

# Get Pending Tree

`GET /trees/{root_hash}/pending`

Fetch a PENDING (staged, not-yet-on-chain) tree by its root hash.

A root is "pending" for a principal when it exists on one of their
accessible vaults' protocol records but is not that vault's active
on-chain root. Once the root is rotated on-chain it is no longer
pending — this endpoint 404s for it and the base /trees/{root_hash}
endpoint serves it instead.

Not cached (unlike the base endpoint): pending status is mutable — a
root graduates on-chain (or is abandoned), which flips this endpoint's
result — so the default no-store applies. The tree blob itself is
content-addressed and immutable, but its accessibility here is not.

## Path parameters

- `root_hash` string, required

## Response `200`

Successful Response

- object

## Other responses

- `401` — Unauthorized — missing or malformed Authorization header.
- `403` — Forbidden — API key invalid, revoked, expired, or insufficient permissions for this action or resource.
- `422` — Validation Error
- `429` — Too Many Requests - Rate limit exceeded

---

[API](https://skmtc.net/veda/apis/veda-console-api.md) · [All operations](https://skmtc.net/veda/apis/veda-console-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/veda/veda-console-api/revisions/2bd8b7cd3078/schema)