Create a sandbox checkpoint
<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>
Saves the app's current state as a checkpoint you can return to.
Every sandbox-bridge endpoint runs against the app's live sandbox, the same filesystem the Base44 builder edits, so a change here is visible in the builder immediately.
This is what makes sandbox work restorable. Writes through this API are committed to git but not checkpointed, and only checkpoints appear in the builder's version history: a Restore or Revert there rolls the app back to the last checkpoint and discards everything written after it. Take a checkpoint when you finish a unit of work and always before you stop, and one before a risky batch of edits so a bad change is one restore away. Pending writes are flushed first, so the checkpoint captures the sandbox as it stands.
Restore it with Restore checkpoint, and list what an app has with List checkpoints. Checkpoints created here show up alongside the ones the builder takes.
This endpoint is limited to 60 requests per minute per app, shared with the other sandbox-bridge endpoints that change files.
<Note>The sandbox bridge needs a Builder plan or higher on the app's workspace, and answers 402 below that. Workspace API keys are not authorized and are rejected with a 403, and it is unavailable for agent apps. A personal API key works as-is. An OAuth access token needs the sandbox:write scope.</Note>
<Tip>Every error response carries a stable extra_data.code alongside the human-readable message. Branch on the code rather than on the message text or the status.</Tip>
Path parameters
ID of the app whose sandbox to operate on.
ID of the app whose sandbox to operate on.
Request body
Response
The checkpoint that was created.
Example response
{
"checkpoint_id": "6886b8d390dc7e2f4a2c91b3",
"name": "Before refactoring the dashboard",
"git_commit_hash": "4f9c1a7e8b2d3c5f6a0b1e2d3c4f5a6b7c8d9e0f"
}