DriveDocument
The body of a drive item of kind document: the rich-editor content plnnrly opens when you click a document in the file browser.
- Summary view
- DriveDocumentList, 6 fields. What a list returns by default.
- Detail view
- DriveDocument, 7 fields. The default for a single read and for every write.
It is stored separately from the item, so the item's own metadata (title, folder, tags, owner, access) lives on the drive item and is not repeated here. The body is exchanged as GitHub-Flavored Markdown, with a sanitised-HTML projection available on demand for the colours, highlights, alignment and mentions Markdown cannot express. Access is inherited whole from the owning drive item: a caller who may read that item may read its body, and a caller who may edit it may write one.
Used by
Fields
- Detail only
- Only in the detail view.
- Only with include
- Only when you ask for it with include.
- Server-assigned
- Set by plnnrly, never by a request.
Id of the document body, not of the drive item it belongs to. The two are numbered separately.
The drive item this body belongs to. Set on create and immutable afterwards; read the item itself from GET /api/v2/drive-items/{drive_item}.
The document body as GitHub-Flavored Markdown: headings, lists, task lists (- [ ]), tables, code fences, links and images all survive. Detail-only: pass ?view=detail to get it on the collection. Markdown cannot express text colours, highlights, alignment or @mentions, so read ?include=content_html first if the document may contain them: a read of content followed by a PATCH of it discards all four permanently.
Last-write timestamp; use for incremental sync. Typing in the collaborative editor moves this, not the drive item's own updated_at.
Variants
DriveDocumentList 6 fields
What a collection returns, and what ?view=summary returns on a single record.
Leaves out: content
DriveDocumentLinks 1 field
The links object on this resource.
Keys: self
Something wrong or missing on this page? Tell us