---
title: "Add a note to a booking"
method: POST
path: "/api/v1/events/{event_id}/notes"
tags: ["Proposals/Confirmed Bookings"]
---

# Add a note to a booking

`POST /api/v1/events/{event_id}/notes`

## Request

- Base URL: `https://api.checkcherry.com`
- URL: `https://api.checkcherry.com/api/v1/events/{event_id}/notes`
- Auth: none declared. Required headers: `Api-Key`

Adds a private internal note to a booking. Notes are visible to staff members only and are never shown to customers. Use them to log internal observations, follow-up activity, or any staff-only context tied to the booking.

Each call appends a new note record with its own author and timestamp (a running timeline), which is distinct from the booking's free-form `public_notes` / `private_notes` text fields on the event itself (those are edited via `PUT /api/v1/events/{event_id}`).

Optionally set or update the booking's next follow-up date in the same call.

**Required permission:** `assigned_event_read` or `unassigned_event_read`

## Path parameters

- `event_id` integer, required

## Headers

- `Api-Key` string, required

## Request body

- object
  - `note` string, required: The note text to add (private internal note, staff-only)
  - `next_follow_up_on` string: Set or update the booking's next follow-up date (YYYY-MM-DD)

## Response `200`

note added

---

[API](https://skmtc.dev/checkcherry/apis/check-cherry-business-api.md) · [All operations](https://skmtc.dev/checkcherry/apis/check-cherry-business-api/llms.txt) · [OpenAPI document](https://skmtc.dev/checkcherry/apis/check-cherry-business-api/revisions/84a9aabdf519?raw)