Lokalise website screenshot

Lokalise

Lokalise is a translation management system (TMS) for software, mobile, web, games, and documentation. It pairs collaborative localization workflows with AI machine translation and a full-coverage REST API (APIv2) that exposes projects, keys, translations, files, contributors, screenshots, snapshots, tasks, branches, glossaries, webhooks, and payments. Official SDKs are maintained for Node.js, Python, Ruby, PHP, Go, Java, .NET, and Elixir.

Lokalise publishes 4 API contracts indexed on the APIs.io network, including Files API, Keys API, Projects API, and 1 more. Tagged areas include Localization, Translation, TMS, AI Machine Translation, and REST.

Lokalise’s developer surface includes authentication, documentation, engineering blog, GitHub presence, and 8 more developer resources.

🌐 Visit website📡 Profile data on GitHub
27.2/100 thin ▼ -6.0 Agent 43/100 agent ready Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
AccessFreeSelf serve⚡ Free to try
1 published contract 1 MCP Servers
LocalizationTranslationTMSAI Machine TranslationRESTDeveloper Tools

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Composite quality — 27.2/100 · thin
Contract Quality 8.5 / 19
Developer Ergonomics 5.4 / 15
Access Clarity 0.8 / 15
Operational Transparency 1.0 / 10
Contract Governance 0.0 / 9
Discoverability 5.6 / 8
Regulatory Posture 1.8 / 15
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 43/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 6 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/lokalise: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

REST
tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Lokalise API v2

Full-coverage REST API for the Lokalise TMS. Resources include projects, keys, translations, contributors, files, comments, screenshots, snapshots, teams, team users, team user ...

Lokalise Files API

The Files API from Lokalise — 1 operation(s) for files.

Lokalise Keys API

The Keys API from Lokalise — 2 operation(s) for keys.

Lokalise Projects API

The Projects API from Lokalise — 2 operation(s) for projects.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Lokalise API v2 Files API

OPEN COLLECTION

Lokalise API v2 Files Keys API

OPEN COLLECTION

Lokalise API v2 Files Projects API

OPEN COLLECTION

Lokalise API v2

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Lokalise MCP Server

Remote MCP server at mcp.lokalise.com over HTTP.

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Lokalise Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lokalise Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Lokalise Finops

FINOPS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lokalise Authentication

apiKey · 1 scheme

SECURITY

Lokalise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Lokalise Agentic Access

10 operations · 6 acting

10 operations · 6 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 LlmsText
LlmsText

Build 1

SDKs, sample code, and the tooling you integrate with

GitHub
GitHub

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits
RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans
Plans
 FinOps
FinOps

Company 3

The organization behind the API

Website
Website
 Blog
Blog
 LinkedIn
LinkedIn

Source (apis.yml)

apis.yml Raw ↑ 
aid: lokalise
url: https://raw.githubusercontent.com/api-evangelist/lokalise/refs/heads/main/apis.yml
name: Lokalise
kind: company
description: Lokalise is a translation management system (TMS) for software, mobile, web, games, and documentation. It pairs
  collaborative localization workflows with AI machine translation and a full-coverage REST API (APIv2) that exposes projects,
  keys, translations, files, contributors, screenshots, snapshots, tasks, branches, glossaries, webhooks, and payments. Official
  SDKs are maintained for Node.js, Python, Ruby, PHP, Go, Java, .NET, and Elixir.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Free · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/lokalise.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Localization
- Translation
- TMS
- AI Machine Translation
- REST
- Developer Tools
created: '2026-05-23'
modified: '2026-05-23'
specificationVersion: '0.23'
apis:
- aid: lokalise:api-v2
  name: Lokalise API v2
  description: Full-coverage REST API for the Lokalise TMS. Resources include projects, keys, translations, contributors,
    files, comments, screenshots, snapshots, teams, team users, team user groups, branches, languages, tasks, glossaries,
    webhooks, payments, and orders. Authentication is via API token in the X-Api-Token header or OAuth 2.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developers.lokalise.com/
  baseURL: https://api.lokalise.com/api2
  tags:
  - REST
  - Project
  - Keys
  - Translation
  - File
  - Contributors
  - Screenshots
  - Webhook
  tags_raw:
  - REST
  - Projects
  - Keys
  - Translations
  - Files
  - Contributors
  - Screenshots
  - Webhooks
  properties:
  - type: Documentation
    url: https://developers.lokalise.com/
  - type: LegacyDocs
    url: https://docs.lokalise.com/en/articles/1400695-lokalise-api-v2
  - type: Blog
    url: https://lokalise.com/blog/lokalise-api/
  - type: SDKs
    title: Node.js
    url: https://github.com/lokalise/node-lokalise-api
  - type: SDKs
    title: Python
    url: https://github.com/lokalise/python-lokalise-api
  - type: SDKs
    title: Ruby
    url: https://github.com/lokalise/ruby-lokalise-api
  - type: SDKs
    title: PHP
    url: https://github.com/lokalise/php-lokalise-api
  - type: SDKs
    title: Go
    url: https://github.com/lokalise/go-lokalise-api
  - type: SDKs
    title: Java
    url: https://github.com/lokalise/java-lokalise-api
  - type: SDKs
    title: .NET
    url: https://github.com/lokalise/dotnet-lokalise-api
  - type: SDKs
    title: Elixir
    url: https://github.com/lokalise/elixir-lokalise-api
- aid: lokalise:lokalise-files-api
  name: Lokalise Files API
  description: The Files API from Lokalise — 1 operation(s) for files.
  humanURL: https://developers.lokalise.com/
  baseURL: https://api.lokalise.com/api2
  tags:
  - File
  tags_raw:
  - Files
  properties:
  - type: OpenAPI
    url: openapi/lokalise-files-api-openapi.yml
- aid: lokalise:lokalise-keys-api
  name: Lokalise Keys API
  description: The Keys API from Lokalise — 2 operation(s) for keys.
  humanURL: https://developers.lokalise.com/
  baseURL: https://api.lokalise.com/api2
  tags:
  - Keys
  properties:
  - type: OpenAPI
    url: openapi/lokalise-keys-api-openapi.yml
- aid: lokalise:lokalise-projects-api
  name: Lokalise Projects API
  description: The Projects API from Lokalise — 2 operation(s) for projects.
  humanURL: https://developers.lokalise.com/
  baseURL: https://api.lokalise.com/api2
  tags:
  - Project
  tags_raw:
  - Projects
  properties:
  - type: OpenAPI
    url: openapi/lokalise-projects-api-openapi.yml
common:
- type: AgenticAccess
  url: agentic-access/lokalise-agentic-access.yml
- type: DomainSecurity
  url: security/lokalise-domain-security.yml
- type: Authentication
  url: authentication/lokalise-authentication.yml
- type: Website
  url: https://lokalise.com/
- type: Documentation
  url: https://developers.lokalise.com/
- type: Blog
  url: https://lokalise.com/blog/
- type: GitHub
  url: https://github.com/lokalise
- type: LinkedIn
  url: https://www.linkedin.com/company/lokalise
- type: Plans
  url: plans/lokalise-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lokalise-rate-limits.yml
- type: FinOps
  url: finops/lokalise-finops.yml
- type: LlmsText
  url: https://developers.lokalise.com/llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/lokalise"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/lokalise/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/lokalise/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.