Glossary term translation taken
What the GlossaryTermTranslationTaken error (409 Conflict) means, the fields it carries, and the endpoints that return it.
The API answers 409 Conflict with this problem. Its type is https://lingo.dev/docs/api/errors/glossary-term-translation-taken. See Errors and status codes for the shape every error shares.
Cannot save "<text>". The glossary already holds its row for "<targetLocale>". Edit that row instead, or change the text.
Fields #
Besides the standard type, status, title and detail members, the body carries these fields. The detail text is built from them, so a client can show its own text instead.
| Field | Type |
|---|---|
text | string |
targetLocale | string |
Example #
json
{
"detail": "Cannot save \"<text>\". The glossary already holds its row for \"<targetLocale>\". Edit that row instead, or change the text.",
"text": "<text>",
"targetLocale": "<targetLocale>",
"type": "https://lingo.dev/docs/api/errors/glossary-term-translation-taken",
"status": 409,
"title": "Glossary term translation taken"
}Returned by #
PATCH /v2/glossaries/{glossaryId}/terms/{id}POST /v2/glossaries/{glossaryId}/termsPOST /v2/glossaries/{glossaryId}/terms/create-many