Codeberg API

Provides a Gitea/Forgejo-compatible REST API for managing git repositories, issues, pull requests, releases, and users on Codeberg, a privacy-focused European open-source code hosting platform.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools git codeberg forgejo gitea open-source privacy europe rest-api
⚙ Agent Friendliness
57
/ 100
Can an agent use this?
🔒 Security
85
/ 100
Is it safe for agents?
⚡ Reliability
74
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
82
Error Messages
78
Auth Simplicity
85
Rate Limits
55

🔒 Security

TLS Enforcement
100
Auth Strength
82
Scope Granularity
80
Dep. Hygiene
80
Secret Handling
82

GDPR-compliant German hosting. API tokens support fine-grained scopes. Webhook payloads include a secret for signature verification. No known history of significant security incidents. Self-hostable if stricter data sovereignty required.

⚡ Reliability

Uptime/SLA
65
Version Stability
80
Breaking Changes
78
Error Recovery
75
AF Security Reliability

Best When

You need a GitHub-alternative REST API with a Gitea-compatible surface area, especially for privacy-conscious projects or FOSS communities preferring European hosting.

Avoid When

Your workflow depends on GitHub-specific ecosystem features (Actions marketplace, GitHub Packages, Dependabot) that have no Codeberg equivalent.

Use Cases

  • Automate repository management — create repos, manage branches, push files, and set webhooks via REST API
  • Manage issues and pull requests programmatically — open issues, add labels, assign reviewers, and merge PRs
  • Retrieve repository content and commit history for analysis, documentation generation, or mirroring pipelines
  • Trigger CI/CD workflows via Woodpecker CI integration and monitor pipeline status through the API
  • Manage releases and assets — create release tags, upload artifacts, and publish changelogs automatically

Not For

  • GitHub-specific features (Actions, Packages registry, Copilot) — Codeberg uses Forgejo/Woodpecker CI with a different feature set
  • Large teams requiring enterprise SSO, advanced audit logs, or compliance certifications (SOC2, FedRAMP)
  • Projects requiring a globally distributed CDN-backed git hosting with guaranteed SLAs

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: api_key basic_auth oauth2
OAuth: Yes Scopes: Yes

API tokens generated in user settings; tokens support fine-grained scopes (repo, issue, org, etc.). OAuth2 application flow available for third-party app integrations. Basic auth supported but deprecated for production use. All requests require Authorization header.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Codeberg is operated by Codeberg e.V., a German non-profit. The service is funded by donations. No commercial tiers or paid plans exist.

Agent Metadata

Pagination
offset
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Codeberg runs Forgejo (a Gitea fork) — the API is compatible with Gitea but not GitHub; agents built against GitHub's API will need significant adaptation
  • Rate limits are not formally documented; agents doing bulk operations should implement conservative rate limiting (1-2 req/s) to avoid triggering anti-abuse measures
  • The OpenAPI spec at /swagger.v1.json is the authoritative reference but may lag behind the deployed version by a release cycle
  • Pagination uses page/limit query parameters (not cursor-based); agents must handle the last page correctly as it may return fewer items than limit
  • Webhook delivery does not include a retry mechanism if the endpoint is unavailable — missed webhooks are lost and cannot be replayed

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Codeberg API.

$99

Scores are editorial opinions as of 2026-03-06.

5208
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered