Read the publish-to-web settings of a standalone view
Returns the standalone view's public configuration, or `enabled: false` when it has never been published. Requires a signed-in workspace session with view read access plus `records:read` on the source database, and a personal view can only be inspected by its owner; only standalone views can be published, so an embedded view or an unknown view is rejected as not publishable.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringviewId*stringSuccess
application/json- response
data*curl -X GET 'https://api.snoze.dev/v1/workspaces/string/views/string/publish'{ "data": { "enabled": true, "slug": "string", "seoIndexed": true, "publishedAt": "string", "updateMode": "snapshot" }}Publish a database to the web
Turns a database into a public read-only data page and returns the stored configuration, deriving the slug from `slug` or the database 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 (`databases:write`) access to the database's item; a database that is not in the workspace tree, or that does not exist, is rejected as not publishable.
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.