Update policy
Update a single policy in place without resending the environment’s full policy list. The policy keeps its id and its position in the evaluation order, and all other policies are untouched.
Omitted fields keep their stored values; at least one updatable field
must be provided. Setting match to null removes all match expressions
so the policy applies to every request. Providing one of keyauth,
ratelimit, firewall or openapi replaces the policy’s rule
entirely, including switching its type; at most one may be set.
Policy ids are regenerated whenever gateway.setPolicies replaces the
list, so fetch current ids via gateway.listPolicies first.
Required Permissions
Your root key must have one of the following permissions:
environment.*.update_policy(for any environment)environment.<environment_id>.update_policy(for a specific environment)
Authorizations
Unkey uses bearer tokens for authentication. Public integrations use root keys, while the dashboard proxy uses short-lived JWTs. To authenticate, include the token in the Authorization header of each request:
Root keys have specific permissions attached to them, controlling what operations they can perform. Legacy permissions use tuple strings like api.*.create_key; resource permissions use Unkey Resource Names plus actions, like unkey:v1:ws_123:keyspaces/*#create_key.
Security best practices:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
Partial update of a single policy. Omitted fields keep their stored
values; at least one updatable field must be provided. Providing one of
keyauth, ratelimit, firewall, openapi or logging replaces the
policy's rule entirely, including switching its type; at most one may be
set.
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.
3 - 255^[a-zA-Z0-9_-]+$"proj_1234abcd"
Id of the policy to update, as returned by gateway.listPolicies.
Ids are regenerated whenever gateway.setPolicies replaces the list,
so list the policies first if you are unsure the id is current.
1 - 512"pol_9d2Fk1LmQ"
New human-readable name. Omit to keep the current name.
1 - 256Enable or disable the policy. Disabled policies are stored but skipped during evaluation. Omit to keep the current setting.
Replaces all match expressions. Set null to remove them so the policy applies to every request. Omit to keep the current expressions.
10Verifies Unkey API keys on matching requests.
Rate limits matching requests. Set identifiers with 1 to 5 sources.
The deprecated identifier field is accepted in place of a one-entry
identifiers list; set exactly one of the two.
Blocks matching requests.
Validates matching requests against the app's uploaded OpenAPI spec. Has no configuration of its own. If no spec has been uploaded for the deployment, the policy is a no-op and requests pass through unvalidated.
Adds request data to the log entries of matching requests. The gateway
always records a basic log entry for every request: method, host, path,
status, and latency. Each capture setting is a separate opt-in: request
headers, response headers, request body, response body, and query data.
The policy's match expressions select the requests. A policy without
match expressions matches every request. If more than one enabled
logging policy matches a request, the gateway combines their settings.
The gateway always redacts the Authorization header and configured key
locations before it stores headers or query data.
Response
Successfully updated the policy.
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId is particularly important when troubleshooting issues with the Unkey support team.
Empty response object by design. A successful response indicates this operation was successfully executed.