---
title: "Every locked version of one commitment's plan of record"
method: GET
path: "/api/v1/commitments/{commitment_id}/money/plan/versions"
tags: ["commitments"]
---

# Every locked version of one commitment's plan of record

`GET /api/v1/commitments/{commitment_id}/money/plan/versions`

## Request

- Base URL: `https://api.app.tightly.io`
- URL: `https://api.app.tightly.io/api/v1/commitments/{commitment_id}/money/plan/versions`
- Auth: HTTP bearer

Every locked version of one commitment's plan of record, newest first, with the version that is the budget flagged. Metadata only: the label, who locked it, when, and how many cells it holds.

A version is the plan as it was, not today's forecast wearing its name: nothing in it is recomputed, which is the whole reason two lines exist. `budget` is the version a variance is measured against, and it is `null` WITH a reason where no version has been named the budget, never an empty object, which would read as a budget of nothing.

An empty list carries its reason, and it is not one reason: nobody has locked a version, or this organisation cannot hold one yet. The frozen grid itself is a separate read, one version at a time, because a year of weekly reforecasts would make this one a download.

Scope: `planning:read`.

## Path parameters

- `commitment_id` string, required

## Headers

- `Tightly-Version` string

## Response `200`

The locked versions of this plan

## Other responses

- `401`: No usable key: malformed, unknown, revoked, expired or stopped. One refusal covers all five, telling a caller which is which maps the surface for them. A request with no Authorization header at all is refused 400 before any key is looked for.
- `403`: The key may not reach this operation. `plan_excludes` when the plan of record is sold with Pro and this organisation's plan does not include it; `scope_missing` when the key does not hold Planning; `organization_mismatch` when the path names an organisation that is not the key's; `ip_not_allowed` when the caller's address is outside the key's allowlist.
- `429`: The key has spent its allowance for this minute. 600 reads and 120 writes a minute, counted per key, refused calls included. `Retry-After` says how long to wait.
- `503`: The database is briefly out of reach, which is what a failover or a full connection pool looks like from outside. Wait the seconds `Retry-After` names and send the request again. A read is safe to repeat. A write is not, because the connection was lost in the middle of it, so read the object back before sending it a second time. Branch on the status rather than on `code`, which is `POSTGRES_UNAVAILABLE` from one of the two seams that raise this and `SERVICE_UNAVAILABLE` from the other.

---

[API](https://skmtc.dev/tightly/apis/tightly-api.md) · [All operations](https://skmtc.dev/tightly/apis/tightly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tightly/apis/tightly-api/revisions/199f7eb35afb?raw)