> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/core-resources/notes.md). # Notes Notes can be linked to clients to support investigations, reviews, and compliance reporting. A **note** can be associated with any client. The API allows you to create, retrieve, update, and delete notes. You can fetch a specific note or retrieve a list of all your notes. ### The Notes object

Attribute	Type	Description
`id`	string	The unique identifier for a note.
`clientId`	string	The ID of the client associated with this note.
`type`	string	The type of note. Valid values are: `report` - included in generated client reports. `internal` - only visible internally and excluded from generated reports.
`note`	string	The content of the note.
`createdAt`	string	The date and time when the note was created.
`updatedAt`	string	The date and time when the note was updated.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.complycube.com/documentation/api-reference/core-resources/notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.