POST
/
v1
/
ratelimits.deleteOverride
curl --request POST \
  --url https://api.unkey.dev/v1/ratelimits.deleteOverride \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "namespaceId": "rlns_1234",
  "namespaceName": "email.outbound",
  "identifier": "user_123"
}'
{}

Changelog

DateChanges
Nov 25 2024Introduced endpoint

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
identifier
string
required

Identifier of your user, this can be their userId, an email, an ip or anything else. Wildcards ( * ) can be used to match multiple identifiers, More info can be found at https://www.unkey.com/docs/ratelimiting/overrides#wildcard-rules

Example:

"user_123"

namespaceId
string

The id of the namespace. Either namespaceId or namespaceName must be provided

Example:

"rlns_1234"

namespaceName
string

The name of the namespace. Namespaces group different limits together for better analytics. You might have a namespace for your public API and one for internal tRPC routes.

Example:

"email.outbound"

Response

200
application/json
Successfully deleted a ratelimit override

The response is of type object.