KV Store: Time-Travel & History

Download Page (.md)

The KV Store on the Hoody platform maintains a full time-travel log of every operation. This page covers the endpoints that let you inspect that history — listing query executions, reconstructing a key or an entire table at any point in time, diffing two snapshots, and rolling back changes. Use these endpoints for auditing, debugging accidental writes, or building undo workflows on top of the KV store.

All endpoints below target the SQLite container’s HTTP interface and share the same per-project host template.

Query History

These endpoints operate on the database-level query log, independent of any specific KV key.

`GET /api/v1/sqlite/history`

Retrieve query execution history for a database. Each entry records the SQL executed, its timestamp, duration, and result summary.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path
`limit`	query	integer	No	Maximum number of entries to return. Default: `100`.

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/history?db=app.db&limit=50"

await client.sqlite.history.list({ db: "app.db", limit: 50 });

{
  "entries": [
    {
      "id": 142,
      "timestamp": 1719436212,
      "sql": "INSERT INTO kv_store (key, value) VALUES ('session:42', '{\"user\":\"alice\"}')",
      "duration_ms": 4,
      "rows_affected": 1,
      "status": "ok"
    },
    {
      "id": 141,
      "timestamp": 1719436205,
      "sql": "SELECT value FROM kv_store WHERE key = 'session:42'",
      "duration_ms": 1,
      "rows_affected": 1,
      "status": "ok"
    }
  ],
  "total": 142,
  "limit": 50,
  "has_more": true
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Invalid db parameter",
  "code": "INVALID_DB_PATH"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

`GET /api/v1/sqlite/history/stats`

Retrieve aggregated statistics over the query history of a database — totals, average durations, top patterns, and error counts.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/history/stats?db=app.db"

await client.sqlite.history.getStats({ db: "app.db" });

{
  "total_entries": 142,
  "first_entry_at": 1719000000,
  "last_entry_at": 1719436212,
  "average_duration_ms": 2.7,
  "total_writes": 89,
  "total_reads": 53,
  "error_count": 0,
  "top_tables": [
    { "table": "kv_store", "hits": 120 },
    { "table": "kv_sessions", "hits": 22 }
  ]
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Invalid db parameter",
  "code": "INVALID_DB_PATH"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to compute statistics",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

`DELETE /api/v1/sqlite/history`

Remove every query history entry associated with a database. This action is irreversible.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path

curl -X DELETE "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/history?db=app.db"

await client.sqlite.history.clear({ db: "app.db" });

{
  "deleted": 142,
  "db": "app.db"
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Invalid db parameter",
  "code": "INVALID_DB_PATH"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to clear history",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

`DELETE /api/v1/sqlite/history/{index}`

Delete a single query history entry identified by its integer ID.

Parameters

Name	In	Type	Required	Description
`index`	path	integer	Yes	History entry ID
`db`	query	string	Yes	Database file path

curl -X DELETE "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/history/142?db=app.db"

await client.sqlite.history.deleteEntry(142, { db: "app.db" });

{
  "deleted": true,
  "id": 142,
  "db": "app.db"
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Invalid db parameter",
  "code": "INVALID_DB_PATH"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "History entry not found",
  "code": "KEY_NOT_FOUND"
}

Error Code	Title	Description	Resolution
`KEY_NOT_FOUND`	Key not found	The requested key does not exist in the KV store	Verify the key name and database/table parameters
`DATABASE_NOT_FOUND`	Database file does not exist	The specified database file was not found	Check the file path or use `create_db_if_missing=true` to create it
`KEY_EXPIRED`	Key expired	The key existed but has expired due to TTL	The key was automatically deleted. Store a new value if needed.

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to delete history entry",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

KV Store Time-Travel

These endpoints reconstruct and manipulate the state of KV keys and tables based on their operation history.

`GET /api/v1/sqlite/kv/{key}/history`

Return every recorded operation on a single key in reverse chronological order. Use it to audit who changed a key and when.

Parameters

Name	In	Type	Required	Description
`key`	path	string	Yes	Key name
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`limit`	query	integer	No	Maximum number of operations to return (0 resolves to default 50, clamped to maximum 1000). Default: `50`.

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/session:42/history?db=app.db&limit=20"

await client.sqlite.kvStore.getHistory("session:42", { db: "app.db", limit: 20 });

{
  "key": "session:42",
  "table": "kv_store",
  "operations": [
    {
      "op_number": 218,
      "op_type": "set",
      "timestamp": 1719436212,
      "value": "{\"user\":\"alice\",\"token\":\"abc123\"}",
      "ttl": null
    },
    {
      "op_number": 215,
      "op_type": "set",
      "timestamp": 1719436001,
      "value": "{\"user\":\"alice\"}",
      "ttl": null
    },
    {
      "op_number": 210,
      "op_type": "create",
      "timestamp": 1719435900,
      "value": "{}",
      "ttl": null
    }
  ],
  "total": 3,
  "has_more": false
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "limit must be a positive integer",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed (e.g. negative limit, malformed integer)	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to read history",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

`GET /api/v1/sqlite/kv/{key}/snapshot`

Reconstruct the value of a key as it appeared at a specific operation number. Combine with the history endpoint to inspect any past state without rolling back.

Parameters

Name	In	Type	Required	Description
`key`	path	string	Yes	Key name
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`op_number`	query	integer	Yes	Operation number to reconstruct from

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/session:42/snapshot?db=app.db&op_number=215"

await client.sqlite.kvStore.getSnapshot("session:42", { db: "app.db", op_number: 215 });

{
  "key": "session:42",
  "table": "kv_store",
  "op_number": 215,
  "reconstructed_at": 1719436001,
  "value": "{\"user\":\"alice\"}",
  "ttl": null,
  "existed_at_op": true
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "op_number is required",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Operation 215 does not exist for this key",
  "code": "KEY_NOT_FOUND"
}

Error Code	Title	Description	Resolution
`KEY_NOT_FOUND`	Key not found	The requested key does not exist in the KV store	Verify the key name and database/table parameters
`DATABASE_NOT_FOUND`	Database file does not exist	The specified database file was not found	Check the file path or use `create_db_if_missing=true` to create it
`KEY_EXPIRED`	Key expired	The key existed but has expired due to TTL	The key was automatically deleted. Store a new value if needed.

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to reconstruct snapshot",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

`GET /api/v1/sqlite/kv/snapshot`

Reconstruct the entire KV table state at a given Unix timestamp. Useful for restoring environments to a known-good point.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`timestamp`	query	integer	Yes	Unix timestamp to reconstruct from
`limit`	query	integer	No	Maximum number of keys to return. Default: `100`.
`prefix`	query	string	No	Filter keys by prefix

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/snapshot?db=app.db&timestamp=1719436000&limit=100&prefix=session:"

await client.sqlite.kvStore.getTableSnapshot({
  db: "app.db",
  timestamp: 1719436000,
  limit: 100,
  prefix: "session:"
});

{
  "table": "kv_store",
  "timestamp": 1719436000,
  "keys": [
    {
      "key": "session:42",
      "value": "{\"user\":\"alice\"}",
      "ttl": null,
      "created_at": 1719435900
    },
    {
      "key": "session:43",
      "value": "{\"user\":\"bob\"}",
      "ttl": 3600,
      "created_at": 1719435950
    }
  ],
  "total": 2,
  "has_gaps": false,
  "gap_keys": [],
  "candidate_truncated": false
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "timestamp must be a Unix epoch integer",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to reconstruct table snapshot",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

{
  "statusCode": 503,
  "error": "Service Unavailable",
  "message": "Request deadline exceeded before commit"
}

`GET /api/v1/sqlite/kv/diff`

Compare the KV table between two Unix timestamps and report which keys were created, modified, or deleted.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`from`	query	integer	Yes	Starting timestamp (Unix)
`to`	query	integer	Yes	Ending timestamp (Unix)
`keys`	query	string	No	Comma-separated list of keys to compare (optional)

curl "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/diff?db=app.db&from=1719435900&to=1719436212&keys=session:42,session:43"

await client.sqlite.kvStore.compareSnapshots({
  db: "app.db",
  from: 1719435900,
  to: 1719436212,
  keys: "session:42,session:43"
});

{
  "table": "kv_store",
  "from_timestamp": 1719435900,
  "to_timestamp": 1719436212,
  "created": [
    {
      "key": "session:43",
      "value": "{\"user\":\"bob\"}",
      "created_at": 1719435950
    }
  ],
  "modified": [
    {
      "key": "session:42",
      "from_value": "{\"user\":\"alice\"}",
      "to_value": "{\"user\":\"alice\",\"token\":\"abc123\"}"
    }
  ],
  "deleted": [],
  "has_gaps": false,
  "gap_keys": [],
  "candidate_truncated": false
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "from must be <= to",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to compute diff",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

{
  "statusCode": 503,
  "error": "Service Unavailable",
  "message": "Request deadline exceeded before commit (large candidate set or heavy maintenance contention)"
}

`POST /api/v1/sqlite/kv/{key}/rollback`

Roll a key back by undoing the last N recorded operations on it. The operation is reversible: you can replay it later using the history endpoint.

Parameters

Name	In	Type	Required	Description
`key`	path	string	Yes	Key name
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`steps`	query	integer	No	Number of operations to rollback. Default: `1`.

This endpoint accepts no request body.

curl -X POST "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/session:42/rollback?db=app.db&steps=1"

await client.sqlite.kvStore.rollback("session:42", { db: "app.db", steps: 1 });

{
  "key": "session:42",
  "table": "kv_store",
  "rolled_back": 1,
  "new_op_number": 219,
  "current_value": "{\"user\":\"alice\"}",
  "previous_value": "{\"user\":\"alice\",\"token\":\"abc123\"}"
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "steps must be >= 1",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed	Check parameter types and values against the API specification
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "No history found for key",
  "code": "KEY_NOT_FOUND"
}

Error Code	Title	Description	Resolution
`KEY_NOT_FOUND`	Key not found	The requested key does not exist in the KV store	Verify the key name and database/table parameters
`DATABASE_NOT_FOUND`	Database file does not exist	The specified database file was not found	Check the file path or use `create_db_if_missing=true` to create it
`KEY_EXPIRED`	Key expired	The key existed but has expired due to TTL	The key was automatically deleted. Store a new value if needed.

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to rollback key",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space

`POST /api/v1/sqlite/kv/rollback`

Roll back an entire KV table to its state at a specific Unix timestamp. This is a destructive operation and requires explicit confirmation via the confirm=yes query parameter. Use dry_run=true first to preview the changes.

Parameters

Name	In	Type	Required	Description
`db`	query	string	Yes	Database file path
`table`	query	string	No	Custom table name. Default: `"kv_store"`.
`to_timestamp`	query	integer	Yes	Target timestamp to rollback to (Unix)
`dry_run`	query	boolean	No	Preview changes without applying. Default: `false`.
`confirm`	query	string	No	Must be `'yes'` to execute actual rollback

Request Body

This endpoint accepts an optional JSON body for filter fields (keys to include or exclude). The server-side schema is open-ended; pass any object you need, or omit the body entirely.

{}

curl -X POST "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/rollback?db=app.db&to_timestamp=1719436000&dry_run=true" \
  -H "Content-Type: application/json" \
  -d '{}'

curl -X POST "https://a1b2c3d4-7890abcdef12-sqlite-1.eu-west-1.containers.hoody.icu/api/v1/sqlite/kv/rollback?db=app.db&to_timestamp=1719436000&confirm=yes" \
  -H "Content-Type: application/json" \
  -d '{}'

await client.sqlite.kvStore.rollbackTable({}, {
  db: "app.db",
  to_timestamp: 1719436000,
  dry_run: true
});

{
  "dry_run": false,
  "table": "kv_store",
  "to_timestamp": 1719436000,
  "rolled_back_keys": 14,
  "created_keys_dropped": 3,
  "modified_keys_restored": 9,
  "deleted_keys_recreated": 2,
  "rollback_op_number": 320
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "confirm=yes is required to execute the rollback",
  "code": "INVALID_PARAMETERS"
}

Error Code	Title	Description	Resolution
`INVALID_DB_PATH`	Invalid database path	The provided database path is invalid or inaccessible	Provide a valid absolute path, or use bare name / `./name` shorthand (resolved to `/hoody/databases/*.db`)
`INVALID_PARAMETERS`	Invalid request parameters	One or more request parameters are invalid or malformed, or `confirm` is missing for an execute call	Check parameter types and values against the API specification; include `confirm=yes` to execute
`INVALID_SQLITE_HEADER`	Not a valid SQLite database	The file exists but is not a valid SQLite database	Ensure the file is a valid SQLite database with proper header
`PATH_IS_DIRECTORY`	Path is a directory	Expected a `.db` file but got a directory (use `table` parameter for directory mode)	Use a `.db` file path or add `table` parameter for directory mode KV store

{
  "statusCode": 409,
  "error": "Conflict",
  "message": "Time-travel chain gap (cannot rollback deterministically)"
}

{
  "statusCode": 500,
  "error": "Internal Server Error",
  "message": "Failed to rollback table",
  "code": "DATABASE_ERROR"
}

Error Code	Title	Description	Resolution
`DATABASE_ERROR`	Database operation failed	An internal database error occurred	Check server logs for details. Database may be corrupted or locked.
`FILE_SYSTEM_ERROR`	File system error	Failed to read or write filesystem in directory mode	Check file permissions and disk space