POST
/
v2
/
ratelimit.deleteOverride
Python (SDK)
from unkey.py import Unkey


with Unkey(
    root_key="<YOUR_BEARER_TOKEN_HERE>",
) as unkey:

    res = unkey.ratelimit.delete_override(namespace="<value>", identifier="premium_user_123")

    # Handle response
    print(res)
{
  "meta": {
    "requestId": "req_123"
  },
  "data": {}
}

Authorizations

​
Authorization
string
header
required

Unkey uses API keys (root keys) for authentication. These keys authorize access to management operations in the API. To authenticate, include your root key in the Authorization header of each request:

Authorization: Bearer unkey_123

Root keys have specific permissions attached to them, controlling what operations they can perform. Key permissions follow a hierarchical structure with patterns like resource.resource_id.action (e.g., apis.*.create_key, apis.*.read_api). 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

Deletes an existing rate limit override. This permanently removes a custom rate limit rule, reverting affected identifiers back to the default rate limits for the namespace.

Use this endpoint when you need to:

  • Remove special rate limit rules that are no longer needed
  • Reset entities back to standard rate limits
  • Clean up temporary overrides
  • Remove outdated tiering or custom limit rules
  • Fix misconfigured overrides

Once deleted, the override cannot be recovered, and the operation takes effect immediately.

Response

200
application/json

Override successfully deleted. Affected identifiers now use default limits.

The response is of type object.