Add Note to Booking

Add a note to a booking for internal tracking or customer communication.

Endpoint

POST /v1/bookings/{id}/notes

Path Parameters

Parameter	Type	Description
id	integer	Booking ID

Request Body

Field	Type	Required	Description
content	string	Yes	Note content (max 5000 chars)

Example Request

curl -X POST "https://app.equipdash.com/api/v1/bookings/123/notes" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Customer requested early pickup at 8am instead of 9am. Confirmed via phone."
  }'

Response

{
  "data": {
    "note": {
      "id": 456,
      "content": "Customer requested early pickup at 8am instead of 9am. Confirmed via phone.",
      "created_at": "2026-02-01T10:00:00+00:00"
    }
  },
  "meta": {
    "request_id": "req_abc123",
    "timestamp": "2026-02-01T10:00:00+00:00"
  }
}

Use Cases

• Special requests: Early pickup, late return, equipment preferences
• Customer communication: Phone calls, emails, in-person discussions
• Internal notes: Staff reminders, follow-ups
• Issue tracking: Problems encountered, resolutions

Notes

• Notes can be added to any booking status (including cancelled)
• API-created notes don't have an associated user
• Notes appear in the booking detail view in the admin
• Notes are included when fetching a booking with GET /v1/bookings/{id}
• Notes cannot be edited or deleted via API

Viewing Notes

When you get a booking, notes are included:

{
  "data": {
    "id": 123,
    "notes": [
      {
        "id": 456,
        "content": "Customer requested early pickup...",
        "created_by": null,
        "created_at": "2026-02-01T10:00:00+00:00"
      },
      {
        "id": 457,
        "content": "Confirmed equipment is available",
        "created_by": {
          "id": 1,
          "name": "John Staff"
        },
        "created_at": "2026-02-01T11:00:00+00:00"
      }
    ]
  }
}

Notes created via API have created_by: null since there's no user session.