Codeberg · Rate Limits

Codeberg Rate Limits

Codeberg does not publish fixed numeric per-account API rate limits. As a donation-funded non-profit running Forgejo, it relies on fair-use expectations rather than a documented per-minute request cap: automated and API use should be reasonable and must not degrade the shared community service. Heavy scraping, bulk cloning, or aggressive automation is discouraged and may be throttled or blocked at the instance and CDN level. Forgejo supports optional per-instance rate limiting configured by administrators, but Codeberg does not publish specific numeric thresholds.

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

It captures 3 rate-limit definitions, measuring requests and operations.

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

Tagged areas include Code Hosting, Git, Non-Profit, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Code HostingGitNon-ProfitRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric per-account API request-rate limit is documented; fair-use expectations apply.
Fair Use instance
requests
reasonable use
Automated/API use must not degrade the shared community service; abusive traffic may be throttled or blocked.
Bulk Automation account
operations
discouraged
Heavy scraping, bulk cloning, and aggressive automation are discouraged on the non-profit instance.

Policies

Fair Use
Codeberg is a shared non-profit resource; API consumers are expected to use it reasonably and not harm availability for the community.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.
Pagination and Caching
Use pagination parameters and cache responses to minimize load rather than repeatedly polling large collections.

Sources