Skip to main content
Client notes can contain private coaching context. Grant note scopes only to trusted server-to-server integrations.

List notes

Required scope:
Query parameters: Note responses omit sorting metadata, coach avatar URLs, and attachment media URLs. Output fields:
Response:

Create a note

Required scope:
Request body fields: Validation: Response fields:
Response (201 Created):

Update a note

Required scope:
Update accepts title, notes, visibleToClient, legacy visibileToClient, pinned, tags[], mentions[], and attachments[] with the validation rules described for create. Update requests are partial, but at least one recognized mutable field must be supplied. The resulting note must still contain content through title, notes, tags, or attachments; an update that would leave the note empty is rejected. Response fields:

Delete a note

Required scope:
Deleting a note permanently removes it. This operation is irreversible.
The delete endpoint returns the standard success envelope with no data payload. Invalid client or note IDs return client errors; inaccessible notes return not found.