The notes endpoints are the core of the Spote API. You can create, read, update, delete, and list notes programmatically. When you create or update a note, Spote automatically generates a semantic embedding so the note is immediately searchable.Documentation Index
Fetch the complete documentation index at: https://docs.spote.cloud/llms.txt
Use this file to discover all available pages before exploring further.
Note object
All endpoints that return a note use this structure:UUID string identifying the note. Use this to reference the note in other endpoints.
The note title.
The note body in Markdown.
The folder the note belongs to. Defaults to
"Inbox".Array of tag strings. Tags do not include the
# prefix.File attachments linked to this note.
ISO 8601 date string of when the note was created.
ISO 8601 date string of when the note was last updated.
POST /api/notes
Create a new note. Spote generates a semantic embedding from the title, bucket, tags, and text automatically.Request body
The note title. Must be at least 1 character.
The note body in Markdown.
The folder to place the note in. If the bucket does not exist, it is created automatically.
Array of tags without the
# prefix. Pass an empty array if the note has no tags.Response
201 Created — returns the full Note object.GET /api/notes
List notes for your account. Results are sorted by creation date, newest first. Supports pagination and filtering by bucket or tag.Query parameters
Maximum number of notes to return.
Number of notes to skip. Use with
limit for pagination.Filter by bucket name. Pass multiple values to include notes from several buckets:
?buckets=Work&buckets=Research.Filter by tag. Pass multiple values to include notes with any of the specified tags:
?tags=ai&tags=ml.Response
200 OK — returns an array of note list items. Embedding fields (embedding, embedding_text) are excluded from list responses.
GET /api/notes/:id
Retrieve a single note by its ID.Path parameters
The note UUID.
Response
200 OK — returns the full Note object including theversion field.
404 Not Found — the note does not exist or belongs to another user.
PUT /api/notes/:id
Update an existing note. All body fields are optional — only the fields you include are updated. If you include aversion, Spote performs conflict detection.
Path parameters
The note UUID.
Request body
Updated title.
Updated Markdown body. Updating
text triggers a new embedding to be generated.Updated bucket name.
Updated tags array without
# prefixes.The version number you last received for this note. If provided, Spote compares this against the database version. If they differ, a
409 is returned instead of applying the update.Response
200 OK — returns the updated Note object with the incrementedversion.
403 Forbidden — you have read-only access to this note via a share.
409 Conflict — the version you sent does not match the current version in the database. The response body contains the current note so you can resolve the conflict.
DELETE /api/notes/:id
Delete a note and all of its shares permanently.Path parameters
The note UUID.