Undo

Undo a change

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.

POST/v1/changesets/{changesetId}/revert

Request

curl --request POST \
  --url 'https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "confirm": true
}'

import json
import requests

url = "https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert"
headers = {
  "Authorization": "Bearer <token>",
  "Content-Type": "application/json"
}
payload = json.loads("{\"confirm\":true}")

response = requests.request("POST", url, headers=headers, json=payload)
print(response.json())

const response = await fetch("https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert", {
  method: "POST",
  headers: {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "confirm": true
  }),
});

const data = await response.json();
console.log(data);

<?php
$client = curl_init();

curl_setopt($client, CURLOPT_URL, "https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert");
curl_setopt($client, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($client, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer <token>",
    "Content-Type: application/json",
]);
curl_setopt($client, CURLOPT_POSTFIELDS, "{\"confirm\":true}");
curl_setopt($client, CURLOPT_RETURNTRANSFER, true);

$response = curl_exec($client);
curl_close($client);
echo $response;

package main

import (
  "bytes"
  "fmt"
  "io"
  "net/http"
)

func main() {
  req, _ := http.NewRequest("POST", "https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert", bytes.NewBuffer([]byte("{\"confirm\":true}")))
  req.Header.Set("Authorization", "Bearer <token>")
  req.Header.Set("Content-Type", "application/json")
  res, _ := http.DefaultClient.Do(req)
  defer res.Body.Close()
  data, _ := io.ReadAll(res.Body)
  fmt.Println(string(data))
}

import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

var request = HttpRequest.newBuilder(URI.create("https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert"))
    .header("Authorization", "Bearer <token>")
    .header("Content-Type", "application/json")
    .method("POST", HttpRequest.BodyPublishers.ofString("{\"confirm\":true}"))
    .build();

var response = HttpClient.newHttpClient().send(
    request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());

require 'net/http'
require 'json'

uri = URI("https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert")
request = Net::HTTP::Post.new(uri)
request["Authorization"] = "Bearer <token>"
request["Content-Type"] = "application/json"
request.body = "{\"confirm\":true}"

response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: uri.scheme == "https") do |http|
  http.request(request)
end

puts response.body

application/json

{
  "data": {
    "id": "<string>",
    "revertId": "<string>",
    "status": "<string>",
    "skipped": [
      {
        "tableId": "<string>",
        "recordId": "<string>",
        "reason": "<string>"
      }
    ]
  }
}

{
  "error": {
    "code": "not_found",
    "message": "<string>",
    "details": {}
  }
}

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

Response

application/json

Success

dataobjectrequired

Show child attributes

idstringrequired

revertIdstring

statusstringrequired

skippedobject[]

curl --request POST \ --url 'https://your-suite.gtable.app/your-app/v1/changesets/<changesetId>/revert' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "confirm": true }'

{ "data": { "id": "<string>", "revertId": "<string>", "status": "<string>", "skipped": [ { "tableId": "<string>", "recordId": "<string>", "reason": "<string>" } ] } }

Undo a change

Path parameters

Headers

Request body

Response

Use these docs with your AI tools

Query these docs via MCP

Query these docs over HTTP

Read these docs as Markdown