Import a glossary file
Merge a CSV or TBX file into the glossary.
Merge a CSV or TBX file into the glossary. Send the file as the raw request body; the format is detected from the content (a body containing <?xml or <martif is read as TBX). A CSV needs a source_term column; part_of_speech, case_sensitive, do_not_translate, forbidden and notes are optional, and every other column named by a locale code holds that locale's translation.
deployTokenAuthorizationBearer <token>A project deploy token, minted in the console under Settings, Developer, API tokens. Send the whole value, including the numeric prefix before the |. A token carries a set of abilities (push, pull, manage, read, write) and each operation requires one of them. Tokens do not inherit from each other: a manage token cannot read the glossary unless it also has read.
body*stringWhat the import did.
application/json- response
imported?integercreated + updated.
created?integerupdated?integerunchanged?integerskipped?integerRows that could not become a term, for example a row with no source term or a value over its length limit.
wording_removed?integerTerms whose stored translations were removed because the file marks them forbidden or do not translate.
wording_ignored?integerTerms the file gives translations for that were not used, because the term is forbidden or do not translate.
no_source_column?booleantrue when a CSV header has no source_term column, so nothing was imported.
curl -X POST 'https://api.transglot.ai/v1/glossary/import'{ "imported": 0, "created": 0, "updated": 0, "unchanged": 0, "skipped": 0, "wording_removed": 0, "wording_ignored": 0, "no_source_column": true}