To map the vocabulary:
An "item" is a "note". A "collection" is also called a collection in the UI.
It's the top level organisation entity within a workspace.
Depending on your environment and how you organise permissions, you may have just one workspace with multiple collections or multiple of both.
This is how to use the Nuclino API at the time of writing to create new notes programmatically in the right places.
To create new notes in Nuclino, make a POST request to:
https://api.nuclino.com/v0/items
Your request should contain the following in addition to header auth:
title - The Title of the the note
content - Note content. You can provide markdown
The API won't accept the request until it knows where the node is going to be created.
You can either provide it with the workspace - If you do, the note will be left at the root of the workspace (ie, 'collection-less!'). Or you can specify the collection.
These are mutually exclusive. The collection UUID is specific enough to identify the workspace within which it was created. Therefore identifying both would be superfluous.
A little confusingly, the collection ID is called parentId. And more confusingly again only the I is capitalised. One of the great advantages of MCP is that it abstracts the challenges of dealing with APIs from humans (sadly, Nuclino does not yet have an MCP!).
So to create a note in a collection with the UUID 1111-1111-111
curl -X POST https://api.nuclino.com/v0/items \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "Your Note Title",
"content": "Your **Markdown** content goes here.",
"parentId": "1111-1111-1111-1111"
}