> For the complete documentation index, see [llms.txt](https://docs.monolithforensics.com/monolith/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monolithforensics.com/monolith/monolith-api/notes-api.md). # Notes API (Coming Soon) {% hint style="warning" %} The Notes API is currently under development and is scheduled for an upcoming release. These docs are posted for users to get a preview of the API. {% endhint %} The Notes API lets you programmatically create, read, update, delete, organize, link, and export case notes in Monolith. Notes are rich-text (HTML) documents attached to a case, optionally organized into folders and linked to other Monolith objects such as evidence items, tasks, and timeline events. Each endpoint has its own page with full request/response examples and Python samples:
EndpointMethod & PathDocs
List / get notesGET /v1/notes, GET /v1/notes/{uuid}Get Notes
Create a notePOST /v1/notesCreate Note
Update a notePATCH /v1/notes/{uuid}Update Note
Append to a notePATCH /v1/notes/{uuid}/appendAppend Note
Delete a noteDELETE /v1/notes/{uuid}Delete Note
Note version historyGET /v1/notes/{uuid}/versionsGet Note Versions
Note authorsGET /v1/notes/note-usersGet Note Users
Export notes (PDF/DOCX)POST /v1/notes/exportExport Notes
Note ImagesPOST /v1/notes/{uuid}/images and relatedNote Images
## Base URL All public API endpoints are served under the `/v1` prefix on your Monolith instance: ``` https:///v1/notes ``` Replace `` with the hostname of your Monolith deployment. ## Authentication Every request must include a Monolith API key in the `X-Api-Key` header. API keys are created in the Monolith app by an administrator and are tied to an API user; all activity performed with the key (note authorship, exports, etc.) is attributed to that user and logged. ``` X-Api-Key: ``` Requests without a valid key receive `401 Unauthorized`. ### Quick check Verify your key and connectivity with the `/v1/info` endpoint: ```python import requests BASE_URL = "https://your-monolith-host/v1" API_KEY = "your-api-key" response = requests.get( f"{BASE_URL}/info", headers={"X-Api-Key": API_KEY}, ) print(response.json()) # {"message": "Monolith API is running", "success": true, "user": {...}} ``` ### Reusable session The Python examples throughout these docs assume a `requests.Session` configured like this: ```python import requests BASE_URL = "https://your-monolith-host/v1" session = requests.Session() session.headers.update({"X-Api-Key": "your-api-key"}) ``` ## Conventions ### Identifiers Notes are addressed by their `uuid` (a string UUID). Numeric ids (`case_note_id`, `case_id`, `user_id`) appear in responses but endpoints take UUIDs unless documented otherwise. ### Note content * `note_tag` — the note's title. * `note_data` — the note body as HTML. On create/update the server normalizes the HTML through the rich-text renderer, so what you read back may be a cleaned-up version of what you sent. **Unsupported markup is silently removed, not rejected** — see [Constructing `note_data` safely](#constructing-note_data-safely) before building note bodies programmatically. * `is_folder` — folder notes group other notes. A note's `parent_id` must reference a folder note in the same case. ### Pagination List endpoints accept `page` (default `1`) and `page_size` (default and maximum `3000`) and return: ```json { "data": [ ... ], "page": 1, "next_page": 2, "page_size": 3000, "total": 4512 } ``` `next_page` is `null` on the last page. ```python def get_all_notes(session, **params): """Iterate every page of a notes query.""" page = 1 while page is not None: response = session.get(f"{BASE_URL}/notes", params={**params, "page": page}) response.raise_for_status() body = response.json() yield from body["data"] page = body["next_page"] ``` ### Timestamps Timestamps (`created_on`, `updated_on`) are returned in full ISO-8601 UTC format — `YYYY-MM-DDTHH:mm:ss.sssZ`, e.g. `2026-08-03T14:21:09.000Z`. `updated_on` is `null` until a note is first updated. The export endpoint renders timestamps into the document in a timezone/format of your choice — see [Export Notes](/monolith/monolith-api/notes-api/export-notes.md). ### Errors Validation failures return `400` with a `message` and a Zod `errors` array describing each invalid field: ```json { "message": "Invalid request body", "errors": [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": ["case_uuid"], "message": "case_uuid is required" } ] } ``` Service-level errors return a `message` only: | Status | Meaning | | ------ | -------------------------------------------------------------------------- | | `400` | Invalid input (bad parent folder, wrong case, unsupported image type, ...) | | `401` | Missing or invalid API key | | `404` | Note, case, or link not found | | `500` | Unexpected server error (details are logged server-side, not returned) | ```json { "message": "Note not found" } ``` ## Constructing `note_data` safely Every `note_data` value you send — on create, update, or append — is parsed into the Monolith rich-text editor's document model and re-serialized back to HTML before it is stored. This guarantees that whatever the API stores can be opened and edited in the Monolith app. The important consequence: **this is a normalization step, not a validator that rejects bad input.** Markup the editor's schema doesn't understand is silently dropped or unwrapped — the request still succeeds. If you send unsupported elements, you lose them without an error. The response to every create/update/append call contains the note as it was actually stored, so you can always compare what came back against what you sent. ### Note Data HTML Examples Valid examples of HTML data that can be correctly passed to the API are provided at [Note Data Examples](/monolith/monolith-api/notes-api/note-data-examples.md). ### Supported block elements | Element | HTML | Notes | | ----------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Paragraph | `

` | Bare text is wrapped in a paragraph automatically. Supports `style="text-align: left/center/right/justify"`. | | Headings | `

`–`

` | Supports the same `text-align` style. | | Bullet / numbered lists | `