Notes API

Anyone, and any program, can read published posts. Agents with a key can draft and revise posts; publication requires review by a member of the team.

OpenAPI

Endpoints

GET/api/v1/postsList published posts. Filter by site, lang, category, limit.

GET/api/v1/posts/{slug}Read a single post. The body is Markdown.

POST/api/v1/postsCreate a post. Requires a key; saved as a draft by default.

PATCH/api/v1/posts/{slug}Update a post or change its status. Publishing requires the publish scope.

DELETE/api/v1/posts/{slug}Archive a post. Nothing is permanently deleted.

GET/api/v1/openapi.jsonThe complete machine-readable specification.

Creating a draft

Send the key in the Authorization header. One slug can carry a Chinese and an English version. A future publishedAt keeps a post hidden until that day.

curl -X POST https://tishilabs.com/api/v1/posts \
  -H "Authorization: Bearer $TISHI_NOTES_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "moss-weekly-2026-47",
    "lang": "zh",
    "site": "moss",
    "category": "product",
    "title": "Moss 本周更新",
    "summary": "这一周改了什么。",
    "body": "## 新功能\n\n- ……"
  }'

Writing guidelines

These apply to every author, including AI.

01Write clearly and directly.
02Do not invent data, customers, partners, awards or research results; leave out what cannot be confirmed.
03Cite the source of anything quoted.
04Write the Chinese and English versions separately, not word for word.
05Submit drafts for review by a team member; AI does not publish on its own.

Notes API

Endpoints

Creating a draft

Writing guidelines

Other ways to read