# RATELIMIT.RESET

> Clear one key's state in a rate limiter so it starts fresh.

URL: https://docs.hotkv.com/commands/ratelimit-reset/

```
RATELIMIT.RESET name key
```

- Group: Rate limiting
- Complexity: O(1)
- HotKV Cloud: Performance and Scale plans
- On-Premise: requires the rate-limiting license feature

Named rate limiters apply one policy (a limit, a window and an algorithm) separately to every key you check against them, such as a user id, an API key or an IP address. `RATELIMIT.RESET` forgets everything the limiter knows about
`key`, so its next request is treated as its first. Other keys are not
affected. It replies `OK` whether or not the key had any state.

## Return value

| Case | RESP2 | RESP3 |
| --- | --- | --- |
| Key reset | Simple string `OK` | Same |

Errors:

- `ERR limiter not found` if the limiter does not exist.
- `ERR wrong number of arguments for 'ratelimit.reset' command` if the argument count is wrong.
- `NOLICENSE rate-limiting requires a HotKV license. Contact sales@hotkv.com` if your license does not include the `rate-limiting` feature.

## Examples

```
127.0.0.1:6379> RATELIMIT.RESET api user:1
OK
127.0.0.1:6379> RATELIMIT.RESET missing user:1
(error) ERR limiter not found
```

## Compatibility

HotKV-only command. Redis and Valkey have no equivalent.

## See also

[RATELIMIT.CREATE](https://docs.hotkv.com/commands/ratelimit-create/index.md), [RATELIMIT.CHECK](https://docs.hotkv.com/commands/ratelimit-check/index.md), [RATELIMIT.PEEK](https://docs.hotkv.com/commands/ratelimit-peek/index.md), [RATELIMIT.STATS](https://docs.hotkv.com/commands/ratelimit-stats/index.md), [RATELIMIT.DROP](https://docs.hotkv.com/commands/ratelimit-drop/index.md), [RATELIMIT.LIST](https://docs.hotkv.com/commands/ratelimit-list/index.md), [AI features guide](https://docs.hotkv.com/ai-features/index.md)