Database endpoints
Delete a row policy
Deletes the row-level security policy for a role on a table.
DELETE /v1/tenants/{tenant}/db/rls
- Identify the role and tableSelect the exact policy to remove.
- Delete the row policyRemove its stored predicate.
- Review resulting accessCheck remaining policies and grants for the role.
Before you start
Use your database bearer token.
Use an identity authorized to manage access in this tenant.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
Query parameters
| Field | Type | Required |
|---|---|---|
table | string | Required |
role | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
deleted reports removal of this role's policy on the table. Removing a row filter can change what that role may read; review the role's grants and remaining policies separately.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 409 | Resolve the conflict before retrying. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 503 | Honor Retry-After when present; check write outcomes. |