Crowdin API

Crowdin's REST API v2 provides programmatic access to translation and localization management including projects, files, translations, translation memory, glossaries, and integrations.

Evaluated Mar 06, 2026 (0d ago) vv2
Homepage ↗ Repo ↗ Developer Tools i18n localization translation l10n rest-api
⚙ Agent Friendliness
59
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
80
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
85
Error Messages
78
Auth Simplicity
80
Rate Limits
68

🔒 Security

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

HTTPS enforced; PATs support scoping; OAuth for delegated access; GDPR and ISO 27001 certified

⚡ Reliability

Uptime/SLA
85
Version Stability
82
Breaking Changes
78
Error Recovery
76
AF Security Reliability

Best When

Software teams managing ongoing localization at scale with multiple contributors and languages

Avoid When

You only need one-off translation and don't need workflow management or TM reuse

Use Cases

  • Automating upload of source strings to translation projects
  • Downloading translated files for release pipelines
  • Managing translation memory and glossary entries
  • Tracking translation progress across languages
  • Integrating localization workflows into CI/CD pipelines

Not For

  • Real-time machine translation (use DeepL or Google Translate instead)
  • Teams needing a free hosted plan beyond open-source projects

Interface

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

Authentication

Methods: api_key oauth2
OAuth: Yes Scopes: Yes

Personal Access Tokens for direct use; OAuth 2.0 for third-party app integrations. Tokens are per-user.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

Open source projects can apply for free unlimited access; commercial projects require paid plans

Agent Metadata

Pagination
offset
Idempotent
Partial
Retry Guidance
Documented

Known Gotchas

  • File uploads require multipart form data, not JSON — agents must handle binary upload correctly
  • Translation approval and review states are separate from translation existence — check status carefully
  • Rate limits vary by plan and are not surfaced clearly in error responses
  • Branch/version management adds complexity to file addressing

Alternatives

Full Evaluation Report

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

$99

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

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