Hanzo
OpenapiCommerce

List your org's notes, as a page

A note is a timestamped free-text log line — a caller-supplied time, a source, a message and an enabled flag.

GET /v1/commerce/note/

Addresshttps://api.hanzo.ai/v1/commerce/note/
MethodGET
Operationget_commerce_note
AuthAuthorization: Bearer $HANZO_API_KEY

A note is a timestamped free-text log line — a caller-supplied time, a source, a message and an enabled flag. That time is the caller's own field and is distinct from the row's creation stamp; the note search filters on it, so a note written without one is a zero-time note the ops log will never surface. Answers a pagination envelope — the page and display echoed back, the rows under models, a total count and a facets array — read from the caller org's own namespaced store, so one tenant can never list another's. Sorting defaults to the last-updated time and is overridable with sort. display is the page size and page applies only alongside it; either one that is not a positive integer is refused with 500 rather than silently ignored, and the limit query overrides the reported COUNT only, never the rows returned. No search backend is wired, so the datastore is the one and only list path and facets is always empty. A request resolving no org namespace is served an EMPTY page rather than an unscoped scan: the namespace IS the tenant filter, so without one there is nothing safe to return. Any valid access token reaches it. The per-kind permission table has no entry for note, so the scaffold skips that second check with a warning and the gate above is the whole authorization story.

Request

GET /v1/commerce/note/ takes no parameters and no body — the credential is the whole request.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo commerce note list

Commerce API · All Hanzo APIs · Interactive reference

How is this guide?

On this page