> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thena.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Notes

> Document and manage account-related information and updates

Notes provide a flexible way to document important information, updates, and insights related to customer accounts in the Thena Platform.

## Understanding notes

<CardGroup cols={1}>
  <Card title="Core purpose" icon="note-sticky">
    Notes serve as a central repository for documenting customer interactions, internal discussions, decisions, and other important account-related information that needs to be preserved and shared across teams.
  </Card>
</CardGroup>

## Note types

<CardGroup cols={2}>
  <Card title="Business notes" icon="briefcase">
    • General updates <br />
    • Meeting minutes <br />
    • Decision records <br />
    • Strategy documents <br />
  </Card>

  <Card title="Technical notes" icon="code">
    • Implementation details <br />
    • Configuration changes <br />
    • Integration notes <br />
    • Troubleshooting logs <br />
  </Card>
</CardGroup>

## Standard fields

### Required fields

| Name       | Type   | Options  | Comments                      |
| :--------- | :----- | :------- | :---------------------------- |
| Account ID | string | Required | Associated account identifier |
| Content    | string | Required | Main content of the note      |

### Optional fields

| Name            | Type   | Options  | Comments                               |
| :-------------- | :----- | :------- | :------------------------------------- |
| Type            | string | Optional | Note type reference                    |
| Visibility      | enum   | Optional | Access control (PUBLIC, PRIVATE, TEAM) |
| Attachment URLs | array  | Optional | List of attachment URLs                |

### System-managed fields

| Name       | Type      | Options        | Comments                       |
| :--------- | :-------- | :------------- | :----------------------------- |
| Note ID    | string    | Auto-generated | Unique identifier for the note |
| UID        | string    | Auto-generated | Unique identifier (ULID)       |
| Is Active  | boolean   | Default: true  | Note's active status           |
| Author ID  | string    | Auto-populated | User who created the note      |
| Created At | timestamp | Auto-populated | Creation timestamp             |
| Updated At | timestamp | Auto-populated | Last update timestamp          |
| Deleted At | timestamp | Optional       | Soft delete timestamp          |

## Note organization

<Steps>
  <Step title="Creation">
    * Choose appropriate type
    * Set clear title
    * Structure content well
    * Add relevant tags
  </Step>

  <Step title="Management">
    * Control visibility
    * Link related records
    * Attach documents
    * Track versions
  </Step>

  <Step title="Collaboration">
    * Share with teams
    * Gather feedback
    * Update content
    * Maintain history
  </Step>
</Steps>

## Best practices

<CardGroup cols={2}>
  <Card title="Content quality" icon="pen-fancy">
    • Write clearly and concisely <br />
    • Use consistent formatting <br />
    • Include relevant context <br />
    • Maintain objectivity <br />
  </Card>

  <Card title="Organization" icon="folder-tree">
    • Use descriptive titles <br />
    • Apply appropriate tags <br />
    • Link related notes <br />
    • Set proper visibility <br />
  </Card>
</CardGroup>

## API endpoints

### Sample note

```json theme={null}
{
  "accountId": "A790SFS229",
  "content": "Met with John (CTO) and Sarah (Engineering Lead) to discuss API integration requirements. Key points:\n- Need OAuth2 implementation\n- Rate limiting concerns for high-traffic periods\n- Webhook setup for real-time updates\n\nNext steps: Schedule technical deep dive next week.",
  "type": "MEETING_NOTES",
  "visibility": "private",
  "attachmentUrls": [
    "https://storage.thena.ai/documents/api-requirements-draft.pdf",
    "https://storage.thena.ai/documents/integration-timeline.xlsx"
  ]
}
```

<Note>
  When creating a note, the system will add additional fields in the response such as:

  * `id`: Unique identifier for the note
  * `account`: Name of the associated account
  * `author`: Name of the note creator
  * `authorId`: ID of the creator
  * `authorEmail`: Email of the creator
  * `createdAt`: Creation timestamp
  * `updatedAt`: Last update timestamp
</Note>

### Available operations

<Accordion title="Note management" icon="note-sticky">
  ```bash theme={null}
  # List account notes
  GET /v1/accounts/{accountId}/notes

  # Create account note
  POST /v1/accounts/{accountId}/notes
  Content-Type: application/json

  # Get note by ID
  GET /v1/accounts/{accountId}/notes/{noteId}

  # Update note
  PATCH /v1/accounts/{accountId}/notes/{noteId}
  Content-Type: application/json

  # Delete note
  DELETE /v1/accounts/{accountId}/notes/{noteId}
  ```

  <Note>
    All endpoints require authentication with Bearer token, API key, and Organization ID in the headers.
  </Note>

  For detailed API specifications, see <a href="/api-reference/platform/accounts/notes" target="_blank">Note Management</a>
</Accordion>

## Related resources

<CardGroup cols={2}>
  <Card title="Accounts overview" icon="building-user" href="/platform/core-concepts/accounts/overview">
    Learn about account management
  </Card>

  <Card title="Activities" icon="calendar-days" href="/platform/core-concepts/accounts/activities">
    Track customer interactions
  </Card>
</CardGroup>