---
title: "Call page.restore_checkpoint"
method: POST
path: "/api/v1/tools/page.restore_checkpoint"
tags: ["page"]
---

# Call page.restore_checkpoint

`POST /api/v1/tools/page.restore_checkpoint`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/page.restore_checkpoint`
- Auth: HTTP bearer

Undo a change to the site the member is working on — 'undo that', 'put it back how it was', 'I liked it better before', 'take that last change back', 'go back to before the build broke'. Every applied edit leaves a checkpoint, so this is the undo for anything that changed the site's source. This is the member's own working copy. No site id is needed — it works on the site the member has open on screen. It restores the site's DRAFT source to a previous checkpoint and rebuilds — the undo for any change to the site's files (name the checkpoint before it in page.checkpoint's ledger). The live site is untouched; the preview follows the rebuild. The checkpoint left behind stays in the ledger, so a rollback can itself be rolled back. A checkpoint whose archive is gone is refused; relay that and offer another. Not for the live site visitors see — that is `page.republish_revision`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `site_id` string, uuid: Optional site UUID. You are NOT shown the id of the site open on screen — it never appears in your context, so there is nothing to copy and nothing to look up. OMIT IT ENTIRELY and this call acts on that on-screen site; that is the PRIMARY path, not a fallback, and the turn's own surface resolves it server-side. Pass it only when the member explicitly named a DIFFERENT site and you took its id from page.list. Never pass a board, board-item, thread or any other id that merely happens to be nearby — those name different objects and will be refused.
  - `source_ref` string, required: The checkpoint to go back to — a source_ref from page.checkpoint's ledger. This changes the DRAFT source and its preview only; the live site is untouched (page.republish_revision is the live one).
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `site_id` string, uuid, required
    - `restored_from_ref` string, required
    - `source_ref` string, required
    - `base_source_ref` string, required
    - `build_run_id` string
    - `build_enqueue_error` string
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)