Knowledge

Folders come first

A note belongs to a folder, so the first call is always the folder list. It returns every folder you can open or manage, your role in each, and whether it is switched on for the assistant.

curl "$MORSE/knowledge/folders" \
  -H "Authorization: Bearer $MORSE_TOKEN"

[
  {
    "id": "8c41f0d2-7a3b-4e19-b5c8-2d6e9f1a4b73",
    "name": "Pricing",
    "role": "manager",
    "is_global": false,
    "active": true
  }
]

The list also carries “Shared with me”, which is not a real folder. It collects notes shared with you directly, whose own folder you cannot open. And a company folder comes back with is_global: true; your role says whether you may add to it.

Write a note

Title, body, and the folder it goes in. Only the title and body are required; leave the folder out and it lands in your own.

curl -X POST "$MORSE/knowledge" \
  -H "Authorization: Bearer $MORSE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Pricing FAQ",
    "body": "Annual plans are billed up front.",
    "folder_id": "8c41f0d2-7a3b-4e19-b5c8-2d6e9f1a4b73"
  }'

Read and change

• GET /knowledge lists what you can see, newest first, each with its folder and what you may do with it.
• GET /knowledge/{doc_id} is one note in full.
• PUT /knowledge/{doc_id} replaces the title or text, and moving a note between folders is the same call with another folder_id, not a separate one.

Every note comes back with can_edit, can_manage, can_move and can_delete. Read those rather than working out permissions yourself. They already account for the folder, the direct shares and whether you are an admin.

Sharing, at two levels

This is the part worth reading twice. A note can be shared by its folder and, separately, on its own. The two are independent: sharing one note out of a private folder does not open the folder.

• GET and PUT /knowledge/folders/{id}/shares: everyone the folder is shared with.
• GET and PUT /knowledge/{doc_id}/shares: everyone this one note is shared with beyond its folder.

curl -X PUT "$MORSE/knowledge/folders/$FOLDER/shares" \
  -H "Authorization: Bearer $MORSE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '[
    { "email": "arjun@neuralarc.ai", "role": "editor" },
    { "id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60", "role": "viewer" }
  ]'

Each entry is a person (email), a team (id) or everyone, as viewer or editor. Only whoever manages the folder may change it.

Feeding the assistant

A folder is only read by the in-meeting assistant when it is switched on for you. This is per person, not per folder. Your colleague switching Pricing off does not switch it off for you.

curl -X PUT "$MORSE/knowledge/folders/$FOLDER/active" \
  -H "Authorization: Bearer $MORSE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "active": true }'

“Shared with me” has its own switch at PUT /knowledge/shared/active, since it is not a folder with an id.

Notes from files

A PDF, Word, Excel, CSV, text or Markdown file can become a note. It is the same three-step upload used everywhere else in the API (ask, send, confirm), and GET /knowledge/uploads tells you first whether this server takes files at all, how large, and of which types.

The note’s own fields are checked before anything is downloaded, so a refusal about the title costs nobody a transfer. The upload is deleted either way; the copy is kept only if the note saves.

The full sequence is in Uploads.

Tidying a paste

POST /knowledge/format proposes a layout for a draft without saving it. It fences the text you send and refuses any reply that adds, removes or changes a word, so it can reformat, never rewrite. Your client decides whether to keep the proposal.

If a tidy was applied and is not wanted, POST /knowledge/{doc_id}/restore-pasted puts the note back exactly as it was pasted.

Every route here is listed with its full schema under Reference → Knowledge.