This feature essentially allows holders of (valid) API keys to bypass any rate limits that have been applied to certain routes (for now it's only /twitch lol).
Most users never hit the rate-limit or even get close to it, since it's relatively generous.
There have been a few edge cases where I've noticed someone spamming requests, but it has usually been unintentional (such as a bug).
A minor difference that this makes when a valid API key is specified, is that the X-RateLimit-* and RetryAfter headers are not included in the responses.
In theory this shouldn't be a problem for any developers to deal with.
This feature essentially allows holders of (valid) API keys to bypass any rate limits that have been applied to certain routes (for now it's only
/twitchlol).Most users never hit the rate-limit or even get close to it, since it's relatively generous.
There have been a few edge cases where I've noticed someone spamming requests, but it has usually been unintentional (such as a bug).
A minor difference that this makes when a valid API key is specified, is that the
X-RateLimit-*andRetryAfterheaders are not included in the responses.In theory this shouldn't be a problem for any developers to deal with.