Skip to main content
POST
/
v2
/
ratelimit.deleteOverride
Typescript (SDK)
import { Unkey } from "@unkey/api";

const unkey = new Unkey({
  rootKey: process.env["UNKEY_ROOT_KEY"] ?? "",
});

async function run() {
  const result = await unkey.ratelimit.deleteOverride({
    namespace: "<value>",
    identifier: "premium_user_123",
  });

  console.log(result);
}

run();
{
  "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.

​
namespace
string
required

The id or name of the namespace containing the override.

Required string length: 1 - 255
​
identifier
string
required

The exact identifier pattern of the override to delete. This must match exactly as it was specified when creating the override.

Important notes:

  • This is case-sensitive and must match exactly
  • Include any wildcards (*) that were part of the original pattern
  • For example, if the override was created for 'premium_', you must use 'premium_' here, not a specific ID

After deletion, any identifiers previously affected by this override will immediately revert to using the default rate limit for the namespace.

Required string length: 1 - 255

Response

Override successfully deleted. Affected identifiers now use default limits.

​
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. A successful response indicates the override was successfully deleted. The operation is immediate - as soon as this response is received, the override no longer exists and affected identifiers have reverted to using the default rate limit for the namespace. No other data is returned as part of the deletion operation.

⌘I