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

# Outbound domain pages: Rebuild the outbound site

> **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 [Outbound domain pages](/docs/api/outbound-site.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Rebuild the outbound site

`POST /v1/outbound-site/refresh` - operationId `outbound-site.refresh`

| Permission | Rate limit |
| --- | --- |
| Delivery edit | 3 requests a day and 10 every 30 days per workspace |

Queues a rebuild of the page from the linked website and answers `202` with the build. The live page changes
when the build's `status` turns `succeeded`; follow it with `latestRun` on
`GET /v1/outbound-site`.

An optional `note` of at most 1,000 characters tells Kenso what to change, such as
`{"note": "drop the pricing section"}`. Each rebuild you start counts against the workspace's limit of 3 a
day and 10 in 30 days. Rebuilds Kenso starts on its own (for the first page, a website change or a content
change) and restores do not count.

Errors:

- `400 validation_failed`: `note` is longer than 1,000 characters.
- `409 website_missing`: neither `mainSiteUrl` nor the workspace website is set.
- `409 run_in_progress`: a build is already queued or running. Wait for it to finish.
- `429 quota_exceeded`: the workspace reached its rebuild limit, and nothing is queued. `Retry-After` and
`quotaResetAt` say when you can rebuild again. `error.details[0]` repeats the limit (`limit`), the
reset time (`resetAt`) and the wait in seconds (`retryAfterSeconds`).

Requires Delivery edit.

Needs the `domain_pages` 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/outbound-site/POST/v1/outbound-site/refresh)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `note` | string | no | What to change in the rebuild, in plain words, such as "drop the pricing section". At most 1,000 characters. Omitted or empty rebuilds with no note. |

### Response 202

`data` is a `OutboundSiteRun`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The build's id. |
| `status` | string | The build's state: `queued`, `running`, `succeeded`, `failed` or `canceled`. The live page changes only when a build succeeds. |
| `trigger` | string | What started the build: `first_page_domain` (the first domain set to show the page), `refresh` (a rebuild a member started), `refresh_with_note` (a rebuild with a note), `website_changed` (the linked website changed) or `content_changed` (Kenso found new content on the linked website). |
| `note` | string | The note sent with the rebuild. Omitted when there is none. |
| `versionId` | integer (int64) | The version the build made. Omitted until the build succeeds. |
| `error` | string | Why the build failed. Omitted when it did not fail. |
| `requestedByUserId` | integer (int64) | The member who started the build. Omitted for a build Kenso started on its own. |
| `createdAt` | string (date-time) | When the build was queued, in UTC. |
| `startedAt` | string (date-time) | When the build started, in UTC. Omitted while it is queued. |
| `finishedAt` | string (date-time) | When the build ended, in UTC. Omitted until it ends. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/outbound-site/refresh" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "note": "string"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "status": "queued",
    "trigger": "string",
    "note": "string",
    "versionId": 812,
    "error": "string",
    "requestedByUserId": 812,
    "createdAt": "2026-09-23T15:02:11Z",
    "startedAt": "2026-09-23T15:02:11Z",
    "finishedAt": "2026-09-23T15:02:11Z"
  }
}
```
