List note journals - Autotouch AI

This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.

Notes and journals are independent, organization-shared resources. Identity, organization, author, timestamps, and harness provenance are server-owned. Developer keys need the endpoint scope; notes:write does not grant notes:read. These calls complete synchronously and do not consume research credits or start scheduled work.

For longitudinal research, create a journal once, then create a new research_update note per observation with journal_id, explicit related_records, observed_at, and sources. Journal links are independent of entry links. Lead, company, and Deal profiles link to their scoped Notes views. Use the existing Scheduled harness for recurrence; note creation itself does not schedule it.

Writes return {note,replayed} or {journal,replayed}. Retrying a committed write with the same key and input returns the resource's current state and replayed=true. Lists return bounded summaries and next_cursor; get and revision reads contain full content. Lists are ordered by created_at descending with ID as tie-breaker. Revision cursors are scoped to one note. DELETE /api/notes/{note_id} archives a note and preserves its revision history; no hard-delete endpoint is exposed. Failed write candidates are excluded from history.

Clients should preserve unknown BlockNote block data when editing; conversion between Markdown and BlockNote is not performed by the API. File uploads, collaborative editing, and revision restoration are not part of this API.

Query parameters

entity_type · optional
string | null
lead, company, or deal. Must be supplied together with entity_id.
entity_id · optional
string | null
Exact linked record ID, paired with entity_type. Filters use both fields from the same link.
limit · optional
integer
Page size 1-100, default 25. Revision pages also stop at about 700 KB; continue with next_cursor.
cursor · optional
string | null
Opaque next_cursor from the previous response. Keep filters unchanged when continuing a list.

Name	Type	Description
entity_type	string \| null	lead, company, or deal. Must be supplied together with entity_id.
entity_id	string \| null	Exact linked record ID, paired with entity_type. Filters use both fields from the same link.
limit	integer	Page size 1-100, default 25. Revision pages also stop at about 700 KB; continue with next_cursor.
cursor	string \| null	Opaque next_cursor from the previous response. Keep filters unchanged when continuing a list.

Errors

Status	Meaning
401	Missing or invalid authentication.
403	Developer key lacks the required Notes scope.
404	Note, journal, or linked record is unavailable in this organization.
409	Stale expected_version or idempotency key reused with changed input.
422	Invalid fields, content bounds, paired record filter, or cursor.

Example

bash

curl -X GET "https://app.autotouch.ai/api/notes/journals" \
  -H "Authorization: Bearer $AUTOTOUCH_API_KEY"

Response example

json

{
  "items": [
    {
      "id": "njournal_example",
      "organization_id": "org_example",
      "title": "Daily research",
      "related_records": [],
      "author_id": "user_example",
      "created_at": "2026-10-02T09:00:00Z"
    }
  ],
  "next_cursor": null
}