SnozeDevelopers
API referenceDatabases

Ensure a record has a content surface

Returns the page-like description surface attached to the record, creating it on the first call. Responds 201 with `created` true when it minted the surface and 200 when one already existed, so repeated calls are safe. Requires the `records:write` permission.

POST
/v1/workspaces/{workspaceId}/databases/{databaseId}/records/{recordId}/content-surface

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
databaseId*string
recordId*string

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X POST 'https://api.snoze.dev/v1/workspaces/string/databases/string/records/string/content-surface'
Example Response
{  "data": {    "workspaceId": "string",    "databaseId": "string",    "recordId": "string",    "surfaceId": "string",    "created": true  }}

Delete a record

Permanently removes the record along with its description surface and returns the deleted row. Requires the `records:write` permission and responds with not-found when the record is not in the database. Set `archived` through an update instead when the record should stay recoverable.

Move a database group to trash

Archives up to 2,000 specified records and hides their group in the selected view in one transaction. A permission, validation, or missing-record failure rolls back the entire change. Requires records:write and views:write permissions; archived records remain recoverable.