Skip to main content
POST
Python (SDK)

Authorizations

Authorization
string
header
required

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

application/json

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 or openapi replaces the policy's rule entirely, including switching its type; at most one may be set.

project
string
required

Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.

Required string length: 3 - 255
Pattern: ^[a-zA-Z0-9_-]+$
Example:

"proj_1234abcd"

app
string
required

Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.

Required string length: 3 - 255
Pattern: ^[a-zA-Z0-9_-]+$
Example:

"proj_1234abcd"

environment
string
required

Identifies a resource by either its unique ID or its slug. Accepts a prefixed ID (such as 'proj_' or 'app_') or a slug.

Required string length: 3 - 255
Pattern: ^[a-zA-Z0-9_-]+$
Example:

"proj_1234abcd"

policyId
string
required

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.

Required string length: 1 - 512
Example:

"pol_9d2Fk1LmQ"

name
string

New human-readable name. Omit to keep the current name.

Required string length: 1 - 256
enabled
boolean

Enable or disable the policy. Disabled policies are stored but skipped during evaluation. Omit to keep the current setting.

match
object[] | null

Replaces all match expressions. Set null to remove them so the policy applies to every request. Omit to keep the current expressions.

Maximum array length: 10
keyauth
object

Verifies Unkey API keys on matching requests.

Example:
ratelimit
object

Rate limits matching requests.

Example:
firewall
object

Blocks matching requests.

Example:
openapi
object

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.

Example:

Response

Successfully updated the policy.

meta
object
required

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.

data
object
required

Empty response object by design. A successful response indicates this operation was successfully executed.

Last modified on July 22, 2026