Skip to content
OpenRelay is in early access, and the /v1 API is stable. New capabilities ship in the changelog.
PricingDashboard
GuidesAPI ReferenceCLI
API ReferenceAccount and accessAccess

Delete a policy

Deletes a guardrail or custom policy and returns 204. A delete is refused with 403 when removing the policy would let the organization do what you cannot. Requires a signed-in session and the permission creating the policy needs.

Required permission

Checked against the guardrail.manage permission for the resource it acts on. See Permissions for the roles and API key permissions that include it.

Command line

The orl CLI wraps this endpoint:

orl authz policy delete <policy-id>
DELETE
/v1/authz/policies/{policyId}

Authorization

apiKey
headerAuthorizationBearer <token>

OpenRelay API key. Send it as Authorization: Bearer or_… (legacy vl_… keys still work).

Path Parameters

policyId*string

Response Body

Deleted

Example Request
curl -X DELETE 'https://api.openrelay.inc/v1/authz/policies/string'
Example Response
Empty

Update, enable or disable a policy PATCH

Changes a policy's name, description, networks, models, endpoints, Cedar text or enabled state, and returns it. Fields left out keep their values. Requires a signed-in session and the permission creating the policy needs.

Get the organization's key settings GET

Returns the organization's maximum API key lifetime in days (0 means keys may never expire), with who last changed it and when.