List ratelimit overrides
Retrieve a paginated list of all rate limit overrides in a namespace.
Use this to audit rate limiting policies, build admin dashboards, or manage override configurations.
Important: Results are paginated. Use the cursor parameter to retrieve additional pages when more results are available.
Permissions: Requires ratelimit.*.read_override or ratelimit.<namespace_id>.read_override
Authorizations
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
Maximum number of override entries to return in a single response. Use this to control response size and loading performance.
- Lower values (10-20): Better for UI displays and faster response times
- Higher values (50-100): Better for data exports or bulk operations
- Default (10): Suitable for most dashboard views
Results exceeding this limit will be paginated, with a cursor provided for fetching subsequent pages.
1 <= x <= 100Response
Overrides retrieved successfully. Includes pagination metadata if more results are available.