Introduction

LingoHub manages the translations of your apps, websites and documents. Its APIs let you automate the work around them: send new source texts in, get finished translations out, and keep LingoHub in step with your code, your content and your release process.

Which API should I use?

	API V2 (Beta)	API V1	CDN API
Use it for	All new integrations	Existing integrations	Loading translations into a running app
Status	Beta: endpoints and fields can still change	Stable, remains supported	Stable
Covers	Workspaces, projects, files, texts, glossaries, automation, integrations and more	Projects, resource files, exports, repository pushes and context images	Distribution releases
Base URL	`https://api.lingohub.com/v2`	`https://api.lingohub.com/v1`	`https://cdn.lingohub.com/v1/distributions`
Authentication	API key	API key	CDN key
Identifiers	Public IDs, for example `pr_019f9d57-…`	URL slugs (`workspaceUrl`, `projectUrl`)	CDN key, plus environment and type in the request body
Errors	RFC 9457 Problem Details with a `code`	HTTP status code with a JSON error body	HTTP status code with a JSON error body

New integrations should use API V2.

The LingoHub CLI (lh-cli) is coming soon. It's updated together with API V2, so once it's released, use it where possible.

Next steps

Create an API key
API V2 (Beta) overview
API V1 overview
Recipes: step-by-step examples for common tasks
Supported file types