Official Libraries
- @unkey/api
- Overview
- Keys
- APIs
- Ratelimits
- @unkey/ratelimit
- @unkey/nextjs
- @unkey/hono
- @unkey/cache
- unkey-go
- unkey.py
- Elixir
- Nuxt
- Rust
- Springboot
Get
Get the configuration for an api key
Request
The ID of the key you want to retrieve.
Response
The id of the key
The first few characters of the key to visually identify it.
The id of the workspace that owns the key
The id of the api that this key is for
The name of the key, give keys a name to easily identify their purpose
The id of the tenant associated with this key. Use whatever reference you have in your system to identify the tenant. When verifying the key, we will send this field back to you, so you know who is accessing your API.
Any additional metadata you want to store with the key
The unix timestamp in milliseconds when the key was created
The unix timestamp in milliseconds when the key was deleted. We don’t delete the key outright, you can restore it later.
The unix timestamp in milliseconds when the key will expire. If this field is null or undefined, the key is not expiring.
The number of requests that can be made with this key before it becomes invalid. If this field is null or undefined, the key has no request limit.
Unkey allows you to refill remaining verifications on a key on a regular interval.
Determines the rate at which verifications will be refilled.
Available options:
daily
: Refills occur every daymonthly
: Refills occur once a month (seerefillDay
for specific day)
Resets remaining
to this value every interval.
value from 1
to 31
.
The day each month to refill ‘remaining’. If no value is given, The 1st will be used as a default.
Read more here
The unix timestamp in miliseconds when the key was last refilled.
Fast ratelimiting doesn’t add latency, while consistent ratelimiting is more accurate.
The total amount of burstable requests.
How many tokens to refill during each refillInterval.
Determines the speed at which tokens are refilled, in milliseconds.