Rate limits on Members API
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
Version history
- Introduced in GitLab 16.9.
You can configure the rate limit per group (or project) per user to the delete members endpoint.
To change the rate limit:
- On the left sidebar, at the bottom, select Admin. If you've turned on the new navigation, in the upper-right corner, select Admin.
- Select Settings > Network.
- Expand Members API rate limit.
- In the Maximum requests per minute per group / project text box, enter the new value.
- Select Save changes.
The rate limit:
- Applies per group or project per user.
- Can be set to 0 to disable rate limiting.
The default value of the rate limit is 60.
Requests over the rate limit are logged into the auth.log file.
For example, if you set a limit of 60, requests sent to the delete members API exceeding a rate of 300 per minute are blocked. Access to the endpoint is allowed after one minute.
Configure rate limits for listing project members
Version history
- Introduced in GitLab 18.6.
Configure the rate limit for listing project members.
To change the rate limit:
- On the left sidebar, at the bottom, select Admin. If you've turned on the new navigation, in the upper-right corner, select Admin.
- Select Settings > Network.
- Expand Members API rate limit.
- In the Maximum requests per minute per group / project text box, enter the new value.
- Select Save changes.
The rate limit:
- Applies per project per user.
- Can be set to 0 to disable rate limits.
The default value of the rate limit is 60.
Requests over the rate limit are logged into the auth.log file.
For example, if you set a limit of 60, requests sent to the list members endpoint project endpoint that exceed a rate of 300 per minute are blocked. Access to the endpoint is allowed after one minute.