Slite · Schema
Note
DocumentationKnowledge BaseCollaborationNotesTeamAsynchronous WorkArtificial IntelligenceSearch
Properties
| Name | Type | Description |
|---|---|---|
| owner | object | Owner of the note for review purposes. Either userId or groupId will be set, but not both. If no owner is set, this field will be omitted. |
| reviewState | object | Review state of the note Can be Verified, Outdated, VerificationRequested or VerificationExpired |
| archivedAt | string | Date of the archiving of the note (null if not archived) |
| lastEditedAt | string | Date of the last edition of the note |
| updatedAt | string | Date of the last update of the note |
| createdAt | string | Date of the creation of the note |
| columns | array | If note is in a collection, it will contain its column names |
| attributes | array | If note is in a collection, it will contain its attributes ordered by column |
| url | string | Url to the note |
| parentNoteId | string | Parent note id of the current note. It can be null if it's a root note. |
| iconColor | string | Optional icon color for the note. |
| iconShape | string | Optional icon identifier for the note. |
| title | string | Title of the note |
| id | string | Id of the note |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/slite/main/json-schema/Note.json",
"title": "Note",
"properties": {
"owner": {
"$ref": "#/components/schemas/NoteOwner",
"description": "Owner of the note for review purposes.\nEither userId or groupId will be set, but not both.\nIf no owner is set, this field will be omitted."
},
"reviewState": {
"$ref": "#/components/schemas/PublicApiReviewState",
"description": "Review state of the note\nCan be Verified, Outdated, VerificationRequested or VerificationExpired"
},
"archivedAt": {
"type": "string",
"format": "date-time",
"nullable": true,
"description": "Date of the archiving of the note (null if not archived)"
},
"lastEditedAt": {
"type": "string",
"format": "date-time",
"description": "Date of the last edition of the note"
},
"updatedAt": {
"type": "string",
"format": "date-time",
"description": "Date of the last update of the note"
},
"createdAt": {
"type": "string",
"format": "date-time",
"description": "Date of the creation of the note"
},
"columns": {
"items": {
"type": "string"
},
"type": "array",
"description": "If note is in a collection, it will contain its column names"
},
"attributes": {
"items": {
"type": "string"
},
"type": "array",
"description": "If note is in a collection, it will contain its attributes ordered\nby column"
},
"url": {
"type": "string",
"description": "Url to the note"
},
"parentNoteId": {
"type": "string",
"nullable": true,
"description": "Parent note id of the current note.\nIt can be null if it's a root note."
},
"iconColor": {
"type": "string",
"nullable": true,
"description": "Optional icon color for the note."
},
"iconShape": {
"type": "string",
"nullable": true,
"description": "Optional icon identifier for the note."
},
"title": {
"type": "string",
"description": "Title of the note"
},
"id": {
"type": "string",
"description": "Id of the note"
}
},
"required": [
"archivedAt",
"lastEditedAt",
"updatedAt",
"createdAt",
"url",
"parentNoteId",
"title",
"id"
],
"type": "object"
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/Note"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.