
SteveM.58178 (Customer) asked a question.
Hi,
This may be silly but in our preview accounts, I can click the edit icon on an API token and clearly see how to throttle or open up rate limits on API tokens. In our production account, however, this options simply doesn't exist on our API token(s). Am I missing something? We have the default settings for rate limits, etc setup in each.
Thanks.
Steve

Hi @SteveM.58178 (Customer) , Thank you for reaching out to the Okta Community!
I've looked into this and the feature is currently only available in Preview environments.
We've got no ETA yet for Production environments but it will be listed in the Okta Release Notes when deployed.
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope it helps!
Thanks for the reply. So given that, what is the percentage rate limit then in our production account for a single API key? Is it 50% ?
Thanks.
Without that feature, the rate limits would not apply per API key. They would be default or whatever you have configured if you have any custom setting in place.
I'm just trying to determine if your documentation saying 50% is accurate for what we have today. As there is no configuration option available on the API token in production, what would the value be? You're saying "default of whatever you have configured if you have any custom setting in place". I don't have any custom setting in place because there's no configuration option available. This is basically the whole question.
Can you please elaborate further on your answer because it's not clear?
Thanks.
With all due respect, have you even read your own documentation?
https://developer.okta.com/docs/reference/rate-limits/#api-rate-limit-categories-and-cumulative-rate-limits
To adjust the default API token capacity value from 50%, you can edit the percentage value in the Admin Console.
You are literally publishing documentation that is not TRUE.
I apologize for the lack of clarity. What I mean to say is that without that feature in effect, the rate limits apply at org level as per the endpoints mentioned in the documentation. API tokens do not have a dedicated rate limit unless you explicitly enable the feature that allows you to configure it.