Add a validation rule to a database
Creates a rule whose `condition` formula must evaluate true for a record to be valid: `block` severity refuses the write and surfaces `message`, while `warn` lets the write through and records the message. Requires the `databases:write` permission and rejects a condition that does not parse. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
workspaceId*stringdatabaseId*stringapplication/json- body
id?|nulllabel*string1 <= length <= 120condition*string1 <= length <= 10000message*string1 <= length <= 1000severity?|nullfieldKey?string|nullorder?number|nullclientMutationId?string|nullSuccess
application/json- response
data*curl -X POST 'https://api.snoze.dev/v1/workspaces/string/databases/string/validation-rules' \ -H 'Content-Type: application/json' \ -d '{ "label": "string", "condition": "string", "message": "string"}'{ "data": { "id": "string", "workspaceId": "string", "databaseId": "string", "label": "string", "condition": "string", "message": "string", "severity": "block", "fieldKey": "string", "enabled": true, "order": 0, "createdAt": "string", "updatedAt": "string" }}List a database's validation rules
Returns the rules that run on every record write, in evaluation order, each with its condition formula, message, severity and the field its message is anchored to. Requires the `databases:read` permission.
Reorder a database's validation rules
Sets the order the rules are evaluated in. `orderedIds` must list every rule on the database exactly once; a partial order is rejected rather than reshuffling the rules it omits. Requires the `databases:write` permission. Send an `Idempotency-Key` header to make retries safe; a replay within the window returns the original response.