The engine's health at a glance (owner only; `datanotes status` prints it): engine, database, journal, git sync, change feed, webhooks, named tokens, hand edits breaking the rules in the last 24 h, logs.
const url = 'https://example.com/datanotes/status/';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/datanotes/status/ \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{}'Reads what the engine already knows (nothing is checked again): hand edits are judged by the checks the change feed recorded with them. healthy is false when problems lists something. A named token is refused (403), even with maintain.
Authorizations
Section titled “Authorizations”Request Body
Section titled “Request Body”object
Example generated
{}Responses
Section titled “Responses”Done.
The engine’s health (datanotes status). Never a token or a secret.
object
False when something needs attention (problems).
What needs attention, in words: git sync blocked, the store backup failing, a webhook failing, the change feed not running, hand edits breaking the tables’ rules, metastore.yaml unreadable.
object
object
How the service sees file changes: events or poll.
The engine’s store folder: settings, tokens, journal, transaction log, change feed, logs.
The database’s id (id in metastore.yaml); its store is found by it.
object
The last move of the database folder: by configure_database, or by hand (found again by its id).
object
Why metastore.yaml is not readable: not found, or the parse error.
Tables keeping a transaction log (history on).
object
The seconds between two looks for changes: when something changed, a commit between two operations, then a push.
The remote, without credentials; null: commits in the store only.
Operations not committed yet.
Commits not pushed yet.
The last failure (a push refused, git missing), until a good push.
When a failing push is tried again.
How to fix last_error, when a person must (a file too large to push).
Where to read more about last_error.
object
Why it is not running.
The newest sequence number, as list_changes answers it.
object
object
The URL’s host only.
Failed attempts in a row (retried with backoff).
The named tokens (never their values).
object
object
Why they were not looked at.
Hand edits the change feed recorded in the window.
Rows whose latest change in the window is a hand edit that breaks the tables’ rules.
object
object
Log files in the store (fileLogEnabled).
--log file.
Origin of the OTLP collector.
Example
{ "database": { "moved": { "by": "configure_database" } }}Bad input: the body is not a JSON object, or an argument is unknown, missing or of the wrong type.
object
What went wrong, for a person or an agent.
Example generated
{ "error": "example"}Missing or wrong bearer token.
object
What went wrong, for a person or an agent.
Example generated
{ "error": "example"}A named token beyond its permissions (the engine’s administration, tables outside its write patterns, schema changes without ddl).
object
What went wrong, for a person or an agent.
Example generated
{ "error": "example"}Unexpected error.
object
What went wrong, for a person or an agent.
Example generated
{ "error": "example"}