> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/sandboxes/openapi.json](/docs/api/sandboxes/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Sandboxes: Reset your sandbox to its seed data

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Sandboxes](/docs/api/sandboxes.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Reset your sandbox to its seed data

`POST /v1/sandboxes/{sandboxId}/reset` - operationId `sandboxes.reset`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 10 requests a day per user |

Deletes everything in the sandbox and seeds it again with the campaigns, contacts, sequences, threads and
analytics a new sandbox starts with. Its test keys and webhook endpoints stay. Returns the sandbox with
`seed` and the new `lastResetAt`. A reset that fails is safe to call again.

- `404 not_found`: the id is not your own sandbox, or the workspace does not have the
`developer_sandboxes` feature.
- `429 quota_exceeded`: you used your 10 sandbox creates and resets of the last 24 hours. They are counted
per member, not per workspace.
- `429 quota_exceeded` with `Retry-After: 30` and the message "Another sandbox is being reset or
deleted. Try again in 30 seconds.": sandbox data is deleted one sandbox at a time, for a reset and for a
delete. A reset refused this way uses none of your creates and resets.

Any member of the header workspace. A request made with a test key is refused. `403 permission_denied`:
a test key or another key held to a permission template, or a Client or Network member seat.
`403 forbidden`: no member is behind the credential.

Needs the `developer_sandboxes` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/sandboxes/POST/v1/sandboxes/%7BsandboxId%7D/reset)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `sandboxId` | path | integer (int64) | yes |  |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `Sandbox`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The sandbox's workspace id. Send it as `X-Ken-Workspace-Id` to work inside the sandbox. |
| `name` | string | The sandbox workspace's name. |
| `status` | string | Always `ready`: a sandbox is usable as soon as it is returned. |
| `createdAt` | string (date-time) | When the sandbox was created (UTC). |
| `lastResetAt` | string (date-time) | When the sandbox was last reset to its seed data (UTC). Omitted until the first reset. |
| `seed` | SandboxSeed | What was seeded. Only on the response of a create or a reset. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/sandboxes/812/reset" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 4102,
    "name": "Sandbox (dana@northwind.example.com)",
    "status": "ready",
    "createdAt": "2026-09-23T15:02:11Z"
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### SandboxSeed

How much seed data a create or a reset wrote into the sandbox.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `campaigns` | integer (int32) | no | Seeded campaigns. |
| `contacts` | integer (int32) | no | Seeded contacts. |
| `inboxes` | integer (int32) | no | Seeded sending inboxes. They are simulated: no mailbox exists behind them. |
| `threads` | integer (int32) | no | Seeded conversation threads. |
