Collected Notes API

Name: Collected Notes API API
Brand: Collected Notes API
Availability: InStock

✓ Official Vendor SpecProductivityNote TakingapiKey14 EndpointsREST

For Agents

Create, update, search, and publish notes on Collected Notes sites and read rendered HTML, links, and back-references through 14 endpoints.

Quickstart

Get started with Collected Notes API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"publish a markdown note"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Collected Notes API API.

Publish a new note with markdown body and visibility flag via POST /sites/{site_id}/notes

Update an existing note's title, body, or visibility via PUT /sites/{site_id}/notes/{note_id}

Full-text search across a site's notes via GET /sites/{site_id}/notes/search

Pull a note's rendered HTML body for embedding via GET /sites/{site_id}/notes/{note_id}/body

GET STARTED

Start building with Collected Notes API API

Explore with Jentic

View OpenAPI Document

Collected Notes is a minimalist writing platform whose API lets developers and agents create, update, search, and publish notes against one or more authored sites. The API exposes 14 endpoints covering note CRUD, full-text search, reorder, link extraction, back-reference lookups, rendered HTML retrieval, and site management. Authentication is via an Authorization header containing a paired email and personal token, scoped to the authenticated user.

Use Cases

Patterns agents use Collected Notes API API for, with concrete tasks.

★ Headless CMS for a Personal Site

Use Collected Notes as a headless CMS by publishing notes via POST /sites/{site_id}/notes and rendering them on a custom front-end with the HTML returned from /sites/{site_id}/notes/{note_id}/body. Each note carries markdown source plus rendered output, so a Next.js or Astro site can fetch content at build time or on demand without running a database. Visibility flags control which notes are public.

Call POST /sites/{site_id}/notes with body containing markdown and visibility='public', then fetch GET /sites/{site_id}/notes/{note_id}/body for the rendered HTML to embed on a Next.js page

AI-Generated Drafts and Updates

Drive content creation from an LLM by generating markdown and posting it via POST /notes/add (which auto-selects the first site) or POST /sites/{site_id}/notes for explicit targeting. Subsequent revisions use PUT /sites/{site_id}/notes/{note_id} so the same note evolves over time. This pattern supports newsletters, daily briefings, and AI-assisted documentation.

Generate a 300-word markdown draft, call POST /notes/add with body and title, then if revisions are needed call PUT /sites/{site_id}/notes/{note_id} with the updated body

Knowledge Graph Across Notes

Build a back-reference map of a knowledge base by walking each note's outbound links via GET /sites/{site_id}/notes/{note_id}/links.json and incoming references via /references.json. Collected Notes exposes both directions of the link graph natively so an agent can answer 'what notes link to this concept?' without reparsing markdown.

Call GET /sites/{site_id}/notes/{note_id}/references.json to list all notes that reference the target, then return their titles and IDs

AI Agent Note Publishing via Jentic

Let an LLM agent publish or update notes on a Collected Notes site by searching Jentic for the operation and executing it. The Authorization header (email + token) is held in the Jentic vault and injected at execution so the agent never sees the credential. Useful for daily summary publishing, lab notebooks, and automated documentation pipelines.

Use Jentic to search 'create a note', load the POST /sites/{site_id}/notes schema, and execute it with the generated markdown body

Key Endpoints

14 endpoints — collected notes is a minimalist writing platform whose api lets developers and agents create, update, search, and publish notes against one or more authored sites.

METHOD

PATH

DESCRIPTION

POST

/sites/{site_id}/notes

Create a note on a site

PUT

/sites/{site_id}/notes/{note_id}

Update an existing note

DELETE

/sites/{site_id}/notes/{note_id}

Delete a note

GET

/sites/{site_id}/notes/search

Search notes within a site

GET

/sites/{site_id}/notes/{note_id}/body

Get rendered HTML body for a note

GET

/sites/{site_id}/notes/{note_id}/references.json

List notes that reference this note

GET

/sites

List your authored sites

POST

/sites/{site_id}/notes

Create a note on a site

PUT

/sites/{site_id}/notes/{note_id}

Update an existing note

DELETE

/sites/{site_id}/notes/{note_id}

Delete a note

GET

/sites/{site_id}/notes/search

Search notes within a site

GET

/sites/{site_id}/notes/{note_id}/body

Get rendered HTML body for a note

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Collected Notes Authorization header (email + token) is stored encrypted in the Jentic vault. Agents never see the email or token; Jentic injects the header at execution.

Intent-based discovery

Agents search by intent (e.g., 'create a note') and Jentic returns the matching Collected Notes operation with its parameter schema so the agent can call the right endpoint without reading docs.

Time to first call

Direct integration: half a day to wire up auth and the email-token format. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ghost Content API

Headless publishing platform with richer theming and member features

Choose Ghost when you need newsletter delivery, member subscriptions, or richer themes alongside content

Alternative

Notion API

Block-based knowledge base with databases and rich content types

Choose Notion when notes need structured properties, databases, or team collaboration features

Complementary

Forem (DEV.to) API

Cross-post the same markdown to a developer community

Pair with Collected Notes when you want a personal canonical site plus distribution to a developer audience

FAQs

Specific to using Collected Notes API API through Jentic.

What authentication does the Collected Notes API use?

Every request requires an Authorization header in the format 'email token', combining the account email and a personal access token. Through Jentic both values live in the encrypted vault and are injected at execution so the credential never enters the agent's prompt.

Can I publish a note without specifying a site ID?

Yes. POST /notes/add creates a note and automatically targets your first site, which is convenient for single-site users. For multi-site accounts use POST /sites/{site_id}/notes with the explicit site ID.

Does Collected Notes return rendered HTML or only markdown?

Both. Notes are authored in markdown but GET /sites/{site_id}/notes/{note_id}/body returns the rendered HTML, so a custom front-end can embed it directly without running a markdown processor.

What are the rate limits for the Collected Notes API?

The OpenAPI spec does not enumerate explicit rate limits. Limits are enforced server-side; requests that exceed them return HTTP 429. For production workloads cache rendered bodies and search results when possible.

How do I publish an AI-generated note through Jentic?

Search Jentic for 'create a note', load the POST /sites/{site_id}/notes schema, and execute it with body, title, and visibility. Jentic injects the Authorization header from the vault and returns the created note's ID and URL.

Can I query the back-references for a note?

Yes. GET /sites/{site_id}/notes/{note_id}/references.json returns notes that link to the target, and /links.json returns its outbound links. Together they expose the bidirectional link graph for knowledge-base use cases.