Intento

Introduction

Glossary

Prerequisites 

Authentication

Common use-cases

Optimize translation workflow

Get Language Quality Insights

Improve translation quality

Segment API

Store segment

Get segments

Search segments

Delete segments

Actions API

Get list of actions

Run action

Get action status

Default

Translation Storage API

Explore Intento's Translation Storage API to efficiently manage, store, and reuse multilingual content. Enhance translation consistency, streamline localization workflows, and reduce costs with AI-powered tools.​

Intento Translation Storage API – Centralized Multilingual Content Management

Production

<p class="slate-p " >The <a href="https://inten.to/translation-storage/" target="">Intento Translation Storage</a> API empowers enterprises to scale their localization efforts with consistency, efficiency, and quality.</p><p class="slate-p " >Centralizing and managing all translated content — across platforms, content sources, and languages — eliminates duplication of translations, reduces costs, and ensures that brand voice is preserved globally.</p><p class="slate-p " >Built to integrate seamlessly with translation workflows and tools, the API enables you to:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Store and reuse translations </strong>to avoid repeated costs and inconsistent output. </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Operate at scale with low latency </strong>with a high-performance architecture optimized for fast segment lookup and write operations under heavy load.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Use AI agents to evaluate and increase the language quality</strong> to ensure it meets your company&apos;s requirements.</div></li></ul><p class="slate-p " >Whether managing a high-volume localization pipeline or building multilingual products, <a href="https://inten.to/translation-storage/" target="">Intento&apos;s Translation Storage</a> API gives you a strategic edge, turning every translation into a long-term asset.</p><p class="slate-p " ></p><p class="slate-p " ></p>

 API empowers enterprises to scale their localization efforts with consistency, efficiency, and quality.

Centralizing and managing all translated content — across platforms, content sources, and languages — eliminates duplication of translations, reduces costs, and ensures that brand voice is preserved globally.

Built to integrate seamlessly with translation workflows and tools, the API enables you to:

Whether managing a high-volume localization pipeline or building multilingual products, 

 API gives you a strategic edge, turning every translation into a long-term asset.

Intento Translation Storage is a centralized solution for managing and reusing multilingual content across your organization. 

<p class="slate-p " >This glossary explains the key terms used throughout the Intento Translation Storage API documentation.  Understanding these definitions is essential for effectively using the API, configuring automated pipelines, and ensuring translation consistency and performance at scale.</p><p class="slate-p " ></p><div class="table-container" style="width:100%;
  min-width:100%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:100px;">Term</div><div style="width:100px;">Description</div><div style="width:100px;">Explanation</div></div><colgroup ><col style="width:initial"><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Segment</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >A discrete text unit (e.g., sentence or paragraph) used for translation. Contains source (initial) and target (translated) text, language pair, and additional metadata.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Stored and managed individually in translation systems to ensure reuse and consistency.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">MT</strong> (Machine Translation)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Automatic translation is produced by machine translation or a GenAI provider without human involvement.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Enables fast and scalable translation. Quality varies by used model, domain, and language pair.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">HT</strong> (Human Translation)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Translation performed or finalized by a human translator.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Linguists ensure that translations meet customer-specific requirements, including tone, terminology, and contextual accuracy. This includes both fully human-generated translations and <strong class="slate-bold">Post-Edited Machine Translation (PEMT)</strong>. Compared to automated options, it typically comes at a higher cost and longer turnaround time.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">APE</strong> (Automatic Post-Editing)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >AI-based improvement of raw MT output using models or rules.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Reduces the need for human editors by automatically correcting linguistic issues.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">LQA</strong> (Language Quality Assessment)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Process of evaluating translation quality and linguistic issue detection.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Reviews and scores content on fluency, accuracy, style, terminology, and customer-specific requirements to maintain consistency.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">TTL</strong> (Time To Live)</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Duration for which a translation remains stored before expiry.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Used for caching MT results only, allowing reuse within a set time window to optimize performance and cost.</p></td></div></tr></tbody></table></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

This glossary explains the key terms used throughout the Intento Translation Storage API documentation.  Understanding these definitions is essential for effectively using the API, configuring automated pipelines, and ensuring translation consistency and performance at scale.

Term

Description

Explanation

Discover essential translation workflow terms in the Intento Translation Storage Glossary. Learn about HT, MT, TTL, APE, LQA, and more — and how they apply to quality, performance, and cost optimization in enterprise localization.

<div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=warning ><div class="callout-icon"><svg width="18" height="16" viewBox="0 0 18 16" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M0.916637 15.5009C0.791637 15.5009 0.683998 15.4732 0.59372 15.4176C0.503443 15.362 0.430526 15.2857 0.37497 15.1884C0.319415 15.0912 0.288165 14.9905 0.28122 14.8864C0.274276 14.7822 0.305526 14.6745 0.37497 14.5634L8.4583 0.605103C8.52775 0.493991 8.60761 0.41413 8.69789 0.365519C8.78816 0.316908 8.88886 0.292603 8.99997 0.292603C9.11108 0.292603 9.21178 0.316908 9.30205 0.365519C9.39233 0.41413 9.47219 0.493991 9.54164 0.605103L17.625 14.5634C17.6944 14.6745 17.7257 14.7822 17.7187 14.8864C17.7118 14.9905 17.6805 15.0912 17.625 15.1884C17.5694 15.2857 17.4965 15.362 17.4062 15.4176C17.3159 15.4732 17.2083 15.5009 17.0833 15.5009H0.916637ZM1.99997 14.2509H16L8.99997 2.1676L1.99997 14.2509ZM9.0833 13.0634C9.26386 13.0634 9.41316 13.0044 9.53122 12.8864C9.64928 12.7683 9.7083 12.619 9.7083 12.4384C9.7083 12.2579 9.64928 12.1086 9.53122 11.9905C9.41316 11.8725 9.26386 11.8134 9.0833 11.8134C8.90275 11.8134 8.75344 11.8725 8.63539 11.9905C8.51733 12.1086 8.4583 12.2579 8.4583 12.4384C8.4583 12.619 8.51733 12.7683 8.63539 12.8864C8.75344 13.0044 8.90275 13.0634 9.0833 13.0634ZM9.0833 10.7509C9.26386 10.7509 9.41316 10.6919 9.53122 10.5739C9.64928 10.4558 9.7083 10.3065 9.7083 10.1259V6.70927C9.7083 6.52871 9.64928 6.37941 9.53122 6.26135C9.41316 6.1433 9.26386 6.08427 9.0833 6.08427C8.90275 6.08427 8.75344 6.1433 8.63539 6.26135C8.51733 6.37941 8.4583 6.52871 8.4583 6.70927V10.1259C8.4583 10.3065 8.51733 10.4558 8.63539 10.5739C8.75344 10.6919 8.90275 10.7509 9.0833 10.7509Z" fill="#F1C21B"></path></svg></div><div ><p class="slate-p " >To enable access to Translation Storage, please <a href="https://inten.to/demo/" target="">book a demo</a> or contact your Intento Customer Success Manager (CSM) directly.</p></div></div><p class="slate-p " >Before integrating with the Intento Translation Storage API, review the following considerations to ensure your setup aligns with operational goals, translation quality, and cost efficiency:</p><p class="slate-p " ><strong class="slate-bold">Translation Storage data isolation strategy</strong></p><p class="slate-p " >Decide whether to use a single, unified Translation Storage for all use cases or multiple to isolate translations between use cases. This choice depends on the diversity of your content and whether different translation requirements (e.g., tone, glossary, quality level) apply. While multiple Translation Storages enable better customization and isolation, they may reduce segment reuse and potentially increase translation costs due to lower caching efficiency.</p><p class="slate-p " ><strong class="slate-bold">Time-To-Live (TTL) for Machine Translation</strong></p><p class="slate-p " >TTL defines how long machine-translated content is stored and reused. It is <strong class="slate-bold">required</strong> to prevent the reuse of outdated results, ensure translations stay up to date with model improvements, support compliance with data retention policies, and optimize cost and performance through controlled caching.</p><div class="slate-div"><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><div class="slate-div"><p class="slate-p " >Human translations (HT) are stored permanently and are not subject to TTL.</p></div></div></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Use of Intento LQA and APE</strong></p><p class="slate-p " >Decide if you plan to use <strong class="slate-bold">Intento</strong> <strong class="slate-bold">LQA</strong> and <strong class="slate-bold">APE</strong>. These features depend on specific language pairs and quality goals. Defining your expectations early helps configure appropriate evaluation models, quality thresholds, and post-editing strategies tailored to your use case.</p></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Before integrating with the Intento Translation Storage API, review the following considerations to ensure your setup aligns with operational goals, translation quality, and cost efficiency:

Translation Storage data isolation strategy

Decide whether to use a single, unified Translation Storage for all use cases or multiple to isolate translations between use cases. This choice depends on the diversity of your content and whether different translation requirements (e.g., tone, glossary, quality level) apply. While multiple Translation Storages enable better customization and isolation, they may reduce segment reuse and potentially increase translation costs due to lower caching efficiency.

Time-To-Live (TTL) for Machine Translation

TTL defines how long machine-translated content is stored and reused. It is 

 to prevent the reuse of outdated results, ensure translations stay up to date with model improvements, support compliance with data retention policies, and optimize cost and performance through controlled caching.

Learn the key prerequisites for using Intento Translation Storage, including authentication setup, API integration requirements, and development environment configuration. Get ready to streamline multilingual content management with AI-powered tools.

<p class="slate-p " >Intento uses API Key authentication method. Every request sent to the Intento Storage API should have a header <code class="slate-code">apikey</code> with a specified key that can be obtained <a href="https://console.inten.to/apikeys" target="_blank">from the console</a>.</p><p class="slate-p " >To learn more about API keys in Intento, visit the <a href="https://help.inten.to/article/360016395119-api-keys" target="">Intento Help Desk</a>. </p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >For each account, Intento provides one production key by default. Requests performed with the production key are via third-party services and billed to your account. Usage limits for production keys are governed by your subscription tier, and additional production keys can be created upon request.</p></div></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Intento uses API Key authentication method. Every request sent to the Intento Storage API should have a header 

 with a specified key that can be obtained 

To learn more about API keys in Intento, visit the 

Understand how to authorize access to Intento Translation Storage. Learn about API key management, secure authentication methods, and best practices for integrating multilingual content workflows.

<p class="slate-p " >This section outlines typical scenarios where the Translation Storage API adds value to your localization workflows. Whether you&apos;re building a multilingual application, optimizing translation costs, or ensuring consistent reuse of approved content, these use cases help you understand how to apply the API effectively.</p><p class="slate-p " ></p>

This section outlines typical scenarios where the Translation Storage API adds value to your localization workflows. Whether you're building a multilingual application, optimizing translation costs, or ensuring consistent reuse of approved content, these use cases help you understand how to apply the API effectively.

Explore practical use cases for Intento Translation Storage, from translation memory reuse and cost optimization to LQA, APE, and multilingual content deployment. Learn how enterprises streamline localization workflows with Intento.

<p class="slate-p " >The <strong class="slate-bold">Segment API</strong> provides core functionality for storing, retrieving, and managing individual translation units (<em class="slate-italic">segments) </em>within Intento&apos;s Translation Storage.</p><p class="slate-p " >Each segment represents a single source string and corresponding translations to the specific language. Segments are uniquely identified by a <strong class="slate-bold">key</strong> (MD5 hash of the source text) to ensure consistency and efficient reuse across projects, vendors, and systems.</p><h4 class="slate-h4 " ><strong class="slate-bold">Key Features:</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Store translations</strong> for any language pair, including metadata. </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Retrieve existing translations</strong> instantly via a key-based lookup. </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Update or delete segments</strong> to keep your translation memory clean and current. </div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Support batch operations</strong> for scalable workflows involving large volumes of content. </div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p>

 provides core functionality for storing, retrieving, and managing individual translation units (

Each segment represents a single source string and corresponding translations to the specific language. Segments are uniquely identified by a 

 (MD5 hash of the source text) to ensure consistency and efficient reuse across projects, vendors, and systems.

Explore the Segment API of Intento Translation Storage to efficiently manage translation segments. Learn how to store, retrieve, search, update, and delete multilingual content using RESTful endpoints.​

<p class="slate-p " >The <strong class="slate-bold">Actions API</strong> enables you to apply advanced, AI-powered <strong class="slate-bold">actions </strong>to translation segments stored in Intento Translation Storage. These actions include <strong class="slate-bold">Automatic Post-Editing (APE)</strong> and <strong class="slate-bold">Language Quality Evaluation (LQE)</strong>, allowing you to assess or enhance the quality of your translations at scale.</p><p class="slate-p " >Actions are fully integrated with stored content and are executed asynchronously via jobs, making it easy to run evaluations or improvements in bulk.</p><h4 class="slate-h4 " >Key Features</h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">List available actions configured for your workspace </div></li><li class="slate-li " ><div style="position:relative">Trigger actions such as APE or LQE on selected segments </div></li><li class="slate-li " ><div style="position:relative">Monitor the status and results of submitted jobs</div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p>

 enables you to apply advanced, AI-powered 

to translation segments stored in Intento Translation Storage. These actions include 

, allowing you to assess or enhance the quality of your translations at scale.

Actions are fully integrated with stored content and are executed asynchronously via jobs, making it easy to run evaluations or improvements in bulk.

Explore the Actions API in Intento Translation Storage to automate and manage translation-related tasks. Learn how to retrieve available actions, execute them, and monitor their status to enhance your localization workflow.​

Sections