Releases API rate limits

Repeated requests that create or update releases, or collect release evidence, can put significant load on your instance. To protect against this, you can limit how often each user and project can write releases, and how often each user can collect evidence.

These rate limits apply to the create a release and update a release REST API endpoints, and to the GraphQL releaseCreate and releaseUpdate mutations, which the GitLab UI also uses. Each create or update request counts toward both limits.

The rate limits:

• Apply per user and per project.
• Default to 600 requests each minute for each user, and 300 requests each minute for each project.
• Can be set to 0 to disable each rate limit.

A separate rate limit applies to the collect release evidence REST API endpoint. It applies per user, defaults to 10 requests each minute, and can be set to 0 to disable it. It does not apply to the evidence that GitLab collects when a release is created, or on the release date of a scheduled release.

If a limit is exceeded, the REST API returns 429 Too Many Requests, and the GraphQL mutations return an error. While a feature flag is disabled, requests over its limit are logged but not blocked.

Change the rate limits

Prerequisites:

• Administrator access.

To change the rate limits:

1. In the upper-right corner, select Admin.
2. In the left sidebar, select Settings > Network.
3. Expand Releases API rate limits.
4. In the Maximum release writes per minute per user, Maximum release writes per minute per project, and Maximum release evidence collections per minute per user text boxes, enter values.
5. Select Save changes.