# Task note put

> Add/update a note to the task

- Source: https://www.taskade.com/docs/rest/task-note-put
- Section: REST API
- Endpoint: `PUT /projects/{projectId}/tasks/{taskId}/note` (API v1)
- Index of all pages: https://www.taskade.com/docs/llms.txt

## PUT `/projects/{projectId}/tasks/{taskId}/note`

Add/update a note to the task

Base URL: `https://www.taskade.com/api/v1`

### Authentication

Send a personal access token or an OAuth 2.0 access token as a bearer token. Create a personal access token at [taskade.com/settings/api](https://www.taskade.com/settings/api).

```http
Authorization: Bearer tskdp_your_token_here
```

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `projectId` | path | `string` | Yes | — |
| `taskId` | path | `string` | Yes | — |

### Request body

`application/json`

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | `string` | Yes | Allowed values: `text/plain`, `text/markdown`. |
| `value` | `string` | Yes | — |

### Example request

```bash
curl -X PUT "https://www.taskade.com/api/v1/projects/<projectId>/tasks/<taskId>/note" \
  -H "Authorization: Bearer $TASKADE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"type":"text/plain","value":"<value>"}'
```

### Responses

#### `200` — Task note set

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ok` | `boolean` | Yes | — |
| `item` | `object` | Yes | — |
| `item.type` | `string` | Yes | The note format. The API writes notes as "text/plain" or "text/markdown". |
| `item.value` | `string` | Yes | — |

A nested field marked Yes is required whenever its parent object is present.

#### `4XX` — Error description

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `ok` | `boolean` | Yes | — |
| `message` | `string` | Yes | — |
| `code` | `string` | Yes | — |
| `statusMessage` | `string` | Yes | — |
| `featureId` | `string` | No | The plan entitlement the request needs, set on some PAYMENT_REQUIRED errors. |

### Errors

Errors return an `ok: false` envelope. Rate limiting returns `429` with `x-rate-limit-limit`, `x-rate-limit-remaining` and `x-rate-limit-reset` headers. `x-rate-limit-reset` is the number of seconds until the window reopens. `Retry-After` is not sent, so schedule retries from `x-rate-limit-reset`; retrying sooner will fail again.

```json
{ "ok": false, "message": "Unauthorized", "code": "UNAUTHORIZED" }
```

Rate limits for this version: enforced per endpoint; ceilings are not published and can change without notice. A `429` response carries `x-rate-limit-limit`, `x-rate-limit-remaining`, and `x-rate-limit-reset` (seconds until the window reopens). Back off from those headers rather than hardcoding numbers. Bundle import and export run under tighter limits than regular reads and writes, so schedule bulk transfers accordingly. See [Rate limits](https://www.taskade.com/docs/getting-started/rest-api-guide#rate-limits).