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

# Sending capacity: Get the sending capacity forecast

> **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 [Sending capacity](/docs/api/sending-capacity.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Get the sending capacity forecast

`GET /v1/sending-capacity/forecast` - operationId `sending-capacity.get-forecast`

| Permission | Rate limit |
| --- | --- |
| Delivery view | 12,000 requests a minute per API key |

Returns the workspace's email forecast for UTC today and the next two days. Each day shows what the healthy
inboxes can send (`capacity`), what is already queued or planned (`planned`) and what is left
(`remaining`). The call takes no parameters.

Kenso plans sends about 36 hours ahead, so `planned` on the later days grows as the planner reaches them.

Requires Delivery view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/sending-capacity/GET/v1/sending-capacity/forecast)

### 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`. |

### Response 200

`data` is a `SendingCapacityForecast`.

| Field | Type | Description |
| --- | --- | --- |
| `calculatedAt` | string (date-time) | When Kenso computed the forecast, in UTC. |
| `days` | array of SendingCapacityForecastDay | Three days in order: UTC today, tomorrow and the day after. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/sending-capacity/forecast" \
  -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": {
    "calculatedAt": "2026-09-23T15:02:11Z",
    "days": [
      {
        "date": "string",
        "capacity": 1,
        "sent": 1,
        "planned": 1,
        "remaining": 1
      }
    ]
  }
}
```

## Types

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

### SendingCapacityForecastDay

One day of the sending forecast.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | string | no | The UTC day, as `YYYY-MM-DD`. |
| `capacity` | integer (int32) | no | Emails the workspace's healthy inboxes can send in one day. Inboxes that Kenso holds back for authentication, complaints, verification, placement, warmup or throttling do not count. All three days show the same figure. |
| `sent` | integer (int32) | no | Emails already sent since UTC midnight. Set on today only and omitted on the later days. |
| `planned` | integer (int32) | no | Emails already queued or planned for the day. Kenso plans about 36 hours ahead, so later days fill in as the planner reaches them. |
| `remaining` | integer (int32) | no | Emails still free for the day: `capacity` minus `sent` and `planned`, never below 0. |
