Gitee · Rate Limits

Gitee Rate Limits

The Gitee Open API v5 enforces per-window request rate limits and returns X-RateLimit-* response headers. On 2026-07-12 an unauthenticated request to GET https://gitee.com/api/v5/repos/oschina/git-osc returned X-RateLimit-Limit: 60 with a decrementing X-RateLimit-Remaining, confirming a 60-requests-per-minute cap for unauthenticated (public) access. Authenticated requests (personal access token or OAuth2) receive a higher allowance. Exceeding the limit yields HTTP 403/429 responses. Some write-heavy or search endpoints may apply additional per-endpoint constraints.

Gitee Rate Limits is the machine-readable rate-limit profile for Gitee on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and throttledAlt.

Tagged areas include Code Hosting, Git, DevOps, Rate Limiting, and Quotas.

2 Limits Throttle: 403
Code HostingGitDevOpsRate LimitingQuotas

Limits

Unauthenticated Requests ip
requests · minute
60
Confirmed live via X-RateLimit-Limit 60 header on an unauthenticated GET.
Authenticated Requests token
requests · minute
higher (not published as a fixed figure)
Personal access token or OAuth2 requests receive a larger allowance than unauthenticated access.

Policies

Rate Limit Headers
Responses include X-RateLimit-Limit and X-RateLimit-Remaining. Read them to pace requests.
Backoff Strategy
On 403/429 throttling, implement exponential backoff with jitter and retry after the window resets.

Sources