---
title: "Undo a change"
description: "Replays a bundle's operations backwards, through the same permission compiler as any other write, so undoing a delete re-creates the row only if you could have created it."
canonical: "https://gtable.app/docs/app-api/changesets/undo"
updated: "2026-10-05"
---

# Undo a change

`POST https://your-suite.gtable.app/your-app/v1/changesets/{changesetId}/revert`

Replays a bundle's operations backwards, through the same permission compiler as any other write, so undoing a delete re-creates the row only if you could have created it.

> **Note: Generic contract**
>
> Your own version of this operation, with your tables and the fields you can read, is in
> your app's document: `https://{suite}.gtable.app/{app}/v1/openapi.json`, behind your credential.
> [Why each person gets their own](/docs/start/studio-and-runtime#why-an-app-has-an-api-of-its-own).

An update puts back ONLY the fields it changed, so a colleague's edit to another field of the same record survives. If somebody has changed one of those same fields since, it refuses and says whose: send `confirm: true` to overwrite theirs anyway. Only a bundle of record creates, edits and deletes can be undone: the changesets list marks each one `revertible`, and anything else (a comment, a saved view, a page, a change to the app's shape) is refused up front with the reason rather than half-applied. Every row it can put back is undone in ONE transaction, and a row deleted since is listed in `skipped` rather than failing the rest.

Requires the `records:write` scope. Operation `changesets.undo`. MCP tool `changesets_undo`. CLI, once published: `gtable changesets undo`.

## Path parameters

| Name          | Type   | Required | Description |
| ------------- | ------ | -------- | ----------- |
| `changesetId` | string | yes      |             |

## Headers

| Name              | Type   | Required | Description                                                                                                                                                                                                                                                        |
| ----------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Idempotency-Key` | string | no       | Any unique string. Sending the same key with the same request again returns the first response (marked `Idempotency-Replayed: true`) instead of running it twice. Reusing it for a different request is refused with 409. Kept for 24 hours. Up to 255 characters. |

## Request body

| Field     | Type    | Required | Description |
| --------- | ------- | -------- | ----------- |
| `confirm` | boolean | no       |             |