## Trilium is in maintenance mode - see details in https://github.com/zadam/trilium/issues/4620
Preliminary disccusions on the successor organization are taking place in [Trilium Next discussions](https://github.com/orgs/TriliumNext/discussions).
[](https://gitter.im/trilium-notes/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [English](https://github.com/zadam/trilium/blob/master/README.md) | [Chinese](https://github.com/zadam/trilium/blob/master/README-ZH_CN.md) | [Russian](https://github.com/zadam/trilium/blob/master/README.ru.md) | [Japanese](https://github.com/zadam/trilium/blob/master/README.ja.md)
[](https://gitter.im/trilium-notes/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [English](https://github.com/zadam/trilium/blob/master/README.md) | [Chinese](https://github.com/zadam/trilium/blob/master/README-ZH_CN.md) | [Russian](https://github.com/zadam/trilium/blob/master/README.ru.md) | [Japanese](https://github.com/zadam/trilium/blob/master/README.ja.md)
Trilium Notes is a hierarchical note taking application with focus on building large personal knowledge bases. See [screenshots](https://github.com/zadam/trilium/wiki/Screenshot-tour) for quick overview:
Trilium Notes is a hierarchical note taking application with focus on building large personal knowledge bases.
See [screenshots](https://github.com/zadam/trilium/wiki/Screenshot-tour) for quick overview:
description:Returns an attachment identified by its ID
operationId:getAttachmentById
responses:
'200':
description:attachment response
content:
application/json; charset=utf-8:
schema:
$ref:'#/components/schemas/Attachment'
default:
description:unexpected error
content:
application/json; charset=utf-8:
schema:
$ref:'#/components/schemas/Error'
patch:
description:patch an attachment identified by the attachmentId with changes in the body. Only role, mime, title, and position are patchable.
operationId:patchAttachmentById
requestBody:
required:true
content:
application/json:
schema:
$ref:'#/components/schemas/Attachment'
responses:
'200':
description:attribute updated
content:
application/json; charset=utf-8:
schema:
$ref:'#/components/schemas/Attachment'
default:
description:unexpected error
content:
application/json; charset=utf-8:
schema:
$ref:'#/components/schemas/Error'
delete:
description:deletes an attachment based on the attachmentId supplied.
operationId:deleteAttachmentById
responses:
'204':
description:attachment deleted
default:
description:unexpected error
content:
application/json; charset=utf-8:
schema:
$ref:'#/components/schemas/Error'
/attachments/{attachmentId}/content:
parameters:
- name:attachmentId
in:path
required:true
schema:
$ref:'#/components/schemas/EntityId'
get:
description:Returns attachment content identified by its ID
operationId:getAttachmentContent
responses:
'200':
description:attachment content response
content:
text/html:
schema:
type:string
put:
description:Updates attachment content identified by its ID
operationId:putAttachmentContentById
requestBody:
description:html content of attachment
required:true
content:
text/plain:
schema:
type:string
responses:
'204':
description:attachment content updated
/attributes:
/attributes:
post:
post:
description:create an attribute for a given note
description:create an attribute for a given note
@ -474,7 +584,7 @@ paths:
schema:
schema:
$ref:'#/components/schemas/Error'
$ref:'#/components/schemas/Error'
patch:
patch:
description:patch a attribute identified by the attributeId with changes in the body. For labels, only value and position can be updated. For relations, only position can be updated. If you want to modify other properties, you need to delete the old attribute and create a new one.
description:patch an attribute identified by the attributeId with changes in the body. For labels, only value and position can be updated. For relations, only position can be updated. If you want to modify other properties, you need to delete the old attribute and create a new one.
operationId:patchAttributeById
operationId:patchAttributeById
requestBody:
requestBody:
required:true
required:true
@ -496,7 +606,7 @@ paths:
schema:
schema:
$ref:'#/components/schemas/Error'
$ref:'#/components/schemas/Error'
delete:
delete:
description:deletes a attribute based on the attributeId supplied.
description:deletes an attribute based on the attributeId supplied.
operationId:deleteAttributeById
operationId:deleteAttributeById
responses:
responses:
'204':
'204':
@ -884,6 +994,57 @@ components:
$ref:'#/components/schemas/Note'
$ref:'#/components/schemas/Note'
branch:
branch:
$ref:'#/components/schemas/Branch'
$ref:'#/components/schemas/Branch'
Attachment:
type:object
description:Attachment is owned by a note, has title and content
properties:
attachmentId:
$ref:'#/components/schemas/EntityId'
readOnly:true
ownerId:
$ref:'#/components/schemas/EntityId'
description:identifies the owner of the attachment, is either noteId or revisionId
role:
type:string
mime:
type:string
title:
type:string
position:
type:integer
format:int32
blobId:
type:string
description:ID of the blob object which effectively serves as a content hash
dateModified:
$ref:'#/components/schemas/LocalDateTime'
readOnly:true
utcDateModified:
$ref:'#/components/schemas/UtcDateTime'
readOnly:true
utcDateScheduledForErasureSince:
$ref:'#/components/schemas/UtcDateTime'
readOnly:true
contentLength:
type:integer
format:int32
CreateAttachment:
type:object
properties:
ownerId:
$ref:'#/components/schemas/EntityId'
description:identifies the owner of the attachment, is either noteId or revisionId
role:
type:string
mime:
type:string
title:
type:string
content:
type:string
position:
type:integer
format:int32
Attribute:
Attribute:
type:object
type:object
description:Attribute (Label, Relation) is a key-value record attached to a note.
description:Attribute (Label, Relation) is a key-value record attached to a note.
&&!awaitdialogService.confirm(`Requested note '${requestedNote.title}' is outside of hoisted note '${hoistedNote.title}' subtree and you must unhoist to access the note. Do you want to proceed with unhoisting?`)){
&&!awaitdialogService.confirm(`Requested note '${requestedNote.title}' is outside of hoisted note '${hoistedNote.title}' subtree and you must unhoist to access the note. Do you want to proceed with unhoisting?`)){