Content
Content is authored material with a draft and a published state, such as a post, an article, or a changelog entry.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
title | string | required | The headline. |
publishedAt | datetime | When it went live. | |
kind | string | What the Content is, so each System reads its own kind. |
Object
{
"$id": "https: //api.sb/ ledgerlark.com/ content/ content_1",
"$type": "Content",
"title": "Monthly close",
"publishedAt": "2026-10-22T12: 00: 00Z",
"kind": "article"
}Relationships
- A Content is displayed on many Pages: Pages display published Content; one piece appears on many Pages.
displayedOn, inversedisplays.
Verbs
createCreates a Content.POST /{namespace}/contentgetReturns one Content by id.GET /{namespace}/content/{id}listReturns Content, newest first, one page at a time.GET /{namespace}/contentupdateChanges the given properties of a Content.PATCH /{namespace}/content/{id}deleteDeletes a Content; its history is kept.DELETE /{namespace}/content/{id}draftDraft writes Content of one kind from a brief, such as an article for a question the help center could not answer.POST /{namespace}/content/draftpublishPublish puts a Content draft live on its Site and every Interface, once it passes the Evals for its kind.POST /{namespace}/content/{content}/publish
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Content.create | Yes | Yes | Yes | No |
Content.get | Yes | Yes | Yes | Yes |
Content.list | Yes | Yes | Yes | Yes |
Content.update | Yes | Yes | Yes | No |
Content.delete | Yes | Yes | Yes | No |
Content.draft | Yes | Yes | Yes | No |
Content.publish | Yes | No | No | No |
Call it
Draft the latest content.Example
A release note for the bulk-export button of a bookkeeping SaaS is Content: drafted by the Product Lead, reviewed, then published to the changelog Page.