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
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_123Root 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:
The id or name of the rate limit namespace to list overrides for.
1 - 255Pagination cursor from a previous response. Include this when fetching subsequent pages of results. Each response containing more results than the requested limit will include a cursor value in the pagination object that can be used here.
Maximum number of override entries to return in a single response. Use this to control response size and loading performance.
Results exceeding this limit will be paginated, with a cursor provided for fetching subsequent pages.
1 <= x <= 100Overrides retrieved successfully. Includes pagination metadata if more results are available.
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.
Pagination metadata for list endpoints. Provides information necessary to traverse through large result sets efficiently using cursor-based pagination.