Daily Notes and Tasks

Summary

Fetches content from daily notes. By default returns blocks from today's daily note. Use 'date' parameter to fetch from other dates.

Use Accept header application/json for structured data, text/markdown for rendered content.

Content Rendering: Text blocks contain markdown formatting. When displaying content, consider rendering markdown as formatted text or cleaning up the syntax for plain text display.

Scope Filtering: Block links in markdown and collections, as well as relations are filtered to daily notes scope (includes all daily notes, task inbox, and task logbook). Block links and date links are returned as block:// and date:// URLs.

Tip: Start by calling GET /documents to list available documents, then use their documentId values as the 'id' parameter to fetch each document's root content.

Summary

Insert content into a daily note. This single endpoint handles both structured blocks and markdown insertion via Content-Type header negotiation.

Content-Type: application/json - Insert structured block objects with position in request body Content-Type: text/markdown - Insert raw markdown text with position specified via query parameter (?position={"position":"end","date":"today"})

Using date-based position targets the most recently updated daily note for that date. To insert into another daily note from the same day, use pageId with the daily note's block ID instead. Multiple daily notes for the same date can occur due to sync conflicts or trash restore, but this is not a core use-case - try using one daily note per day whenever possible.

Returns the inserted blocks with their assigned block IDs for later reference.

Summary

Delete content from daily notes. Removes specified blocks by their IDs.

Summary

Update content in daily notes. For text blocks, provide updated markdown content. Only the fields that are provided will be updated.

Summary

Move blocks to reorder them or move them to a different daily note. Returns the moved block IDs.

Summary

Get all items from a collection

Summary

Add new items to a collection. Two-way relations are synced automatically in the background - only set one side for consistency.

Summary

Delete collection items (also deletes content inside items)

Summary

Update collection items. Two-way relations are synced automatically in the background - only set one side for consistency.

Summary

Set the collection-level activeViewId to one existing collection view ID. This only changes which stored view is marked active; it does not execute the view or change collection items.

Summary

List table, gallery, and kanban view definitions for a collection. This returns configuration only; it does not execute filters/sorts/groups or return collection items. If activeViewId is missing or invalid, the first stored view is treated as active.

Summary

Create a collection view definition. Use type table for the regular/default table layout, gallery for card layouts, or kanban for grouped boards. This creates configuration only; it does not create or return collection items. Kanban requires exactly one group rule.

Summary

Delete one collection view definition by view ID. Cannot delete the last stored view in a collection. If the active view is deleted, the first remaining stored view becomes active.

Summary

Update one collection view definition by view ID. Omitted settings are preserved. Pass empty arrays or objects to clear list-like settings. Gallery settings are only valid for gallery views; kanban settings are only valid for kanban views.

Summary

List all collections across daily notes. Use optional startDate and endDate query parameters to filter collections by daily note date range.

Summary

Create a new collection (structured table) in a daily note. Position date defaults to 'today'. Define the schema with columns and their types.

Summary

Get collection schema in JSON Schema format

Summary

Update the collection schema. Replaces the existing schema entirely - include all fields you want to keep. Keep property keys stable for existing properties.

Summary

Add comments to blocks.

Summary

Returns connection metadata including space ID, space name, timezone, current time, and URL templates for constructing deep links to blocks.

Summary

Experimental: list block reminders within this connection's document scope. See the Reminders section for availability and ownership.

Summary

Experimental: set or replace reminders on blocks within this connection's document scope. Omit the time to Save for later.

Summary

Experimental: delete block reminders within this connection's document scope. The blocks themselves are not deleted.

Summary

Experimental: update block reminders within this connection's document scope. Only provided fields are changed.

Summary

Search content within a specific daily note. Supports regex patterns for flexible searching. Use the 'date' query parameter to specify which daily note to search (defaults to 'today').

Summary

Search content across multiple daily notes using relevance-based ranking. This endpoint uses FlexiSpaceSearch to find matches across your daily notes within an optional date range.

Key Features:

• Search across multiple daily notes (vs /blocks/search which searches a single daily note)
• Include term filtering
• Optional date range filtering (startDate/endDate)
• Relevance-based ranking (top 20 results)
• Context blocks before/after each match
• Supports relative dates: 'today', 'tomorrow', 'yesterday'

Example Use Cases:

• Find all mentions of a project across the last month
• Search for meeting notes from a specific time period
• Locate tasks or action items across multiple days

Summary

Retrieve tasks. Tasks are automatically organized into inbox, active, upcoming, and logbook categories.

Summary

Create new tasks in inbox or daily notes. Tasks can include schedule dates and deadlines.

Summary

Delete tasks by their IDs. Only tasks in inbox, logbook, or daily notes can be deleted.

Summary

Update existing tasks. Can modify task content, state, schedule dates, and deadlines. Marking tasks as done/canceled moves them to logbook.

Summary

Upload a file (image, video, or document) and insert it at the specified position. Send raw binary data in request body with Content-Type header.

Summary

Create a new empty whiteboard block at the specified position. Returns the whiteboard block ID. Use whiteboardElements_add to populate it.

Summary

Get all Excalidraw elements and appState from a whiteboard block.

Summary

Append elements to an existing whiteboard without removing existing ones.

Summary

Remove elements from a whiteboard by their Excalidraw element IDs.

Summary

Update specific elements in a whiteboard by their ID. Elements not included in the request remain unchanged.