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

# Access requests: Create an access request

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

## Create an access request

`POST /v1/access-requests` - operationId `access-requests.create`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 30 requests a minute per API key |

Asks for a page, a feature or a higher monthly credit limit for the caller. Kenso notifies every member who has
the `members` permission, and one of them grants or declines the request.

Set `kind` to `page`, `feature` or `credits`:

- `page`: `key` is a page name such as `campaigns`, and `level` is `view` or `edit`.
Without `level`, the request asks for one level above what the caller has now.
- `feature`: `key` is a feature name such as `launch`. Do not send `level`.
- `credits`: `key` is `monthly_limit`. Do not send `level`. The member who grants it sets the new limit.

`reason` is an optional note of up to 2,000 characters for the people who decide.

The caller can have one pending request for the same `kind` and `key`. Asking again returns that
request with 200 instead of 201 and sends no new notification.

Errors:

- `400 validation_failed`: `kind`, `key`, `level` or `reason` is invalid. The detail code
`already_granted` means the caller already has this access, or has no monthly credit limit to raise.

Open to any workspace member.

Needs the `permissions` 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/access-requests/POST/v1/access-requests)

### 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 |
| --- | --- | --- | --- |
| `kind` | string | yes | Required. What to ask for: `page`, `feature` or `credits`. |
| `key` | string | yes | Required. A page name such as `campaigns`, a feature name such as `launch`, or `monthly_limit` for a credits request. |
| `level` | string | no | Page requests only: `view` or `edit`. Omitted asks for one level above the caller's current access. |
| `reason` | string | no | An optional note for the people who decide, up to 2,000 characters. |

### Response 201

Also answers `200`. `data` is a `AccessRequest`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The id of the access request. |
| `kind` | string | What the member asks for: `page`, `feature` or `credits`. |
| `key` | string | The page name for a `page` request, the feature name for a `feature` request, or `monthly_limit` for a `credits` request. |
| `level` | string | The level asked for on a page request: `view` or `edit`. Omitted on other requests. |
| `reason` | string | The requester's note for the people who decide. Omitted when they wrote none. |
| `status` | string | Where the request stands: `pending`, `granted`, `declined` or `canceled`. |
| `requesterId` | integer (int64) | The member who asked. A member id is the member's Kenso user id. |
| `decidedById` | integer (int64) | The member who granted, declined or canceled the request. Omitted while it is pending. |
| `decidedAt` | string (date-time) | When the request was granted, declined or canceled, in UTC. Omitted while it is pending. |
| `createdAt` | string (date-time) | When the member made the request, in UTC. |
| `updatedAt` | string (date-time) | When the request last changed, in UTC. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/access-requests" \
  -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 '{
  "kind": "page",
  "key": "campaigns",
  "level": "view",
  "reason": "string"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "kind": "page",
    "key": "string",
    "level": "view",
    "reason": "string",
    "status": "pending",
    "requesterId": 812,
    "decidedById": 812,
    "decidedAt": "2026-09-23T15:02:11Z",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z"
  }
}
```
