SnozeDevelopers
API referenceDatabase publish

Publish a standalone view to the web

Turns a standalone database view into a public read-only page and returns the resulting configuration, deriving the slug from `slug` or the view label and de-duplicating it against every published page, database, and view in the one global `/wp` address space. Requires a signed-in workspace session with full (`views:write`) access to the view and `records:read` on its source database; a personal view can only be published by its owner, and non-standalone or unknown views are rejected. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.

PUT
/v1/workspaces/{workspaceId}/views/{viewId}/publish

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
viewId*string

Request Body

application/json
  1. body
slug?string|null
seoIndexed?boolean|null
updateMode?|null

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X PUT 'https://api.snoze.dev/v1/workspaces/string/views/string/publish' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "data": {    "enabled": true,    "slug": "string",    "seoIndexed": true,    "publishedAt": "string",    "updateMode": "snapshot"  }}

Withdraw a standalone view from the web

Disables the view's public page while retaining its slug, and records the change on the workspace event ledger; a view that was never published is left untouched. Requires a signed-in workspace session with full (`views:write`) access to the view, and ownership as well when the view is personal. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.

Read a published database or view by its public slug

Returns the viewer payload for a database or standalone view that has been published to the web: title, icon, workspace name, indexing preference, the visible fields, and the first page of records (capped, with `hasMore` set when more exist). No authentication; the `slug` in the path is the credential. A slug that is unknown, unpublished, or not readable returns the same opaque not-found response, and time-tracking data is stripped from the payload.