Skip to content

Overview

Eurotext runs a translation service. You push text in, humans (and their tooling) translate it, you pull the result back out. The v2 REST API is how you automate that instead of emailing spreadsheets around.

The mental model is small:

  • A project is a container. It has a name, a description, and a status.
  • A project holds items. One item = one source unit (a product, an article, a page) with its fields.
  • Each item is translated from one source language into one target language.
  • You start a project, then poll it until every item comes back finished.

That's really it. The rest of these docs are about the details that aren't obvious from the endpoint list — language codes, how status is reported, how to carry your own IDs through the round-trip.

Typical integration shape

For something like an Akeneo connector you end up with two moving parts:

  1. A push step (on demand or batched): collect the products that need translation, create a project, add an item per product, start it. Store the returned project id next to your records.
  2. A poll step (cron or queue worker): walk the open project ids, check status, and when one is delivered, fetch the items and write the translations back where they belong.

Delivery is not instant — it's human translation, so think hours to days. The push step is cheap; the poll step is where you spend your patience.

Where to start