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.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
curl -X PUT "https://example.com/v1/workspaces/string/databases/string/publish" \ -H "Content-Type: application/json" \ -d '{}'{ "data": { "enabled": true, "slug": "string", "seoIndexed": true, "publishedAt": "string" }}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}Withdraw a database from the web
Disables the database's public page while retaining its slug, so republishing later reuses the same address; a database that was never published is left untouched. Requires a signed-in workspace session with full (`databases:write`) access to the database's item.
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.