Hjarni REST API
The REST API is for scripts, automations, and custom integrations. If you are connecting an AI assistant like ChatGPT or Claude, use the MCP server instead.
Overview
https://hjarni.com/api/v1application/jsonAuthentication
- Go to Settings > Connections in Hjarni.
- Create a token for your integration.
- Send it in the
Authorizationheader as a Bearer token.
curl https://hjarni.com/api/v1/notes \
-H "Authorization: Bearer YOUR_API_TOKEN"
Pagination
List endpoints accept page (default 1) and per_page (default 25, max 100). Metadata is returned in response headers:
X-Total-CountX-PageX-Per-PageDashboard
/api/v1/dashboard
Overview of your personal knowledge base with counts and recent notes.
Response example
{
"inbox_count": 3,
"notes_count": 42,
"archived_count": 7,
"containers_count": 8,
"tags_count": 12,
"recent_notes": [
{
"id": 1,
"title": "Weekly review",
"body": "# Decisions\n\n...",
"summary": "Review of the week",
"source_url": null,
"archived": false,
"favorited": false,
"position": 1,
"created_at": "2026-03-15T10:00:00Z",
"updated_at": "2026-03-15T10:00:00Z",
"tag_list": "review,planning",
"tags": [{"id": 1, "name": "review"}, {"id": 2, "name": "planning"}],
"container": {"id": 5, "name": "Work"},
"files": []
}
]
}
Search
/api/v1/search
Full-text search across notes. Returns paginated note objects.
qsearch_scope"personal", "all" (default), or "team:<id>" for a specific team.page, per_pageGET /api/v1/search?q=weekly+planning&search_scope=personal
Notes
/api/v1/notes
List personal notes. Paginated.
scope"archived", "inbox", "favorited", or omit for active notes.container_idtagqpage, per_page/api/v1/notes/inbox
Notes without a container. Paginated. Same response shape as listing notes.
/api/v1/notes/:id
Full note with body, tags, container, files, and linked note IDs.
Response example
{
"id": 1,
"title": "Weekly review",
"body": "# Decisions\n\nSee [[42:Project plan]].",
"summary": "Review of the week",
"source_url": "https://example.com/source",
"archived": false,
"favorited": true,
"position": 1,
"created_at": "2026-03-15T10:00:00Z",
"updated_at": "2026-03-15T12:30:00Z",
"tag_list": "review,planning",
"tags": [
{"id": 1, "name": "review"},
{"id": 2, "name": "planning"}
],
"container": {"id": 5, "name": "Work"},
"files": [
{
"id": 10,
"description": "Slide deck",
"filename": "slides.pdf",
"content_type": "application/pdf",
"byte_size": 204800,
"url": "https://hjarni.com/rails/active_storage/blobs/..."
}
],
"linked_note_ids": [42, 58]
}
/api/v1/notes
Create a note. Returns 201 on success.
titlebody[[id:Title]] wiki-links.summarysource_urlcontainer_idtag_list"review,planning".positionPOST /api/v1/notes
{
"note": {
"title": "Weekly review",
"body": "# Weekly review\n\nKey decisions...",
"summary": "Review of the week",
"source_url": "https://example.com/source",
"container_id": 12,
"tag_list": "review,planning"
}
}
/api/v1/notes/:id
Update any note field. Only include the fields you want to change.
PATCH /api/v1/notes/1
{
"note": {
"body": "Updated content",
"tag_list": "review,done"
}
}
Optional expected_lock_version guards against concurrent edits. Every note read returns a lock_version integer. Echo it back on your write and the server rejects with 409 Conflict if someone else saved in the meantime.
PATCH /api/v1/notes/1
{
"note": {
"body": "Updated content",
"expected_lock_version": 5
}
}
# 409 Conflict response when the version no longer matches:
{
"error": "Note was modified since you last read it. Re-read and re-apply...",
"current_lock_version": 7,
"last_edited_by": "alice@example.com",
"last_edited_by_agent": null,
"last_edited_at": "2026-05-27T14:32:00Z"
}
Surgical body edits (replace_find, insert_after, append_body) are anchor-based and stay safe with or without the version. Pass expected_lock_version whenever you also touch non-body fields and want a stale-write guard.
For long notes, prefer the structured patch operations over a full-body replacement — they target a heading or checklist item instead of the whole document, so a stale read can't clobber unrelated sections. Each targets exactly one match and is mutually exclusive with the other body modes.
replace_section + section_body#), keeping the heading line. The section runs to the next same-or-higher-level heading.append_to_section + section_bodyrename_heading + new_headingnew_heading carries its own # markers.check_item / uncheck_itemship it). Matched case- and whitespace-insensitively.PATCH /api/v1/notes/1
{
"note": {
"append_to_section": "## Open Questions",
"section_body": "- Should we ship Friday?"
}
}
/api/v1/notes/:id
Permanently delete a note. Returns 204.
Note actions
PATCH /notes/:id/archive
Archive a note. Returns the updated note.
PATCH /notes/:id/unarchive
Restore an archived note. Returns the updated note.
PATCH /notes/:id/favorite
Mark a note as favorited. Returns the updated note.
PATCH /notes/:id/unfavorite
Remove from favorites. Returns the updated note.
PATCH /notes/:id/move
Move to another container. Send {"container_id": 5}.
Note links
POST /notes/:id/link
Link two notes bidirectionally. Send {"target_note_id": 42}. Returns the source note.
DELETE /notes/:id/unlink
Remove the link. Send {"target_note_id": 42}. Returns 204.
GET /notes/:id/linked
List all notes linked to this note. Returns an array of note objects.
Containers
/api/v1/containers
List containers. Paginated. Returns root-level containers by default.
scope"archived", "all" (all active, flat), or omit for active roots only.Response example
[
{
"id": 5,
"name": "Work",
"description": "Day job projects",
"position": 1,
"archived": false,
"llm_instructions": "Use formal tone.",
"created_at": "2026-03-01T09:00:00Z",
"updated_at": "2026-03-15T10:00:00Z",
"notes_count": 12,
"children_count": 3,
"parent": null
}
]
/api/v1/containers/:id
Single container with counts and parent info.
/api/v1/containers
Create a container. Returns 201.
namedescriptionparent_idllm_instructionspositionPOST /api/v1/containers
{
"container": {
"name": "Research",
"description": "Papers and reading notes",
"parent_id": 5
}
}
/api/v1/containers/:id
Update name, description, parent, position, or instructions.
/api/v1/containers/:id
Delete a container. Notes inside it are moved to the inbox. Child containers become root-level. Returns 204.
Container actions
PATCH /containers/:id/archive
Archive. Returns the updated container.
PATCH /containers/:id/unarchive
Restore. Returns the updated container.
GET /containers/:id/children
Direct child containers. Returns an array of container objects.
GET /containers/:id/notes
Notes in this container. Paginated.
GET /containers/:id/tree
Container with its ancestor chain and direct children.
PATCH /containers/reorder
Reorder containers. Send {"ordered_ids": [3,1,2]} with all IDs in the scope. Optional parent_id to reorder children of a specific container. Returns 204.
Root instructions
GET /containers/root_instructions
Get your personal root AI instructions. Returns {"personal_llm_instructions": "..."}.
PATCH /containers/update_root_instructions
Update root instructions. Send {"personal_llm_instructions": "..."}.
Errors
401
Missing or invalid token.
403
Plan-gated action, such as exceeding the Free plan note limit or attempting file uploads without a paid plan. Response includes an error message and upgrade_url.
404
Resource not found or not accessible by your account.
422
Validation failed. Response includes an errors array with messages.
Questions about the API?
Email evert@hjarni.com and we'll help.
Give your AI a memory. Free.
Connect Claude or ChatGPT to notes they can actually read and write.
Give your AI a memory. Free.