XTM Cloud_logo

Extension

XTM Cloud Extension

Seamless GenAI Workflows for your XTM projects

Generative AI Translation, Machine Translation Post-Editing, Translation Quality Estimation, and Terminology Validation inside your XTM translation projects

The Custom.MT XTM Extension connects your XTM Cloud translation management system to our enterprise translation API. This integration automates custom machine translation, machine translation post-editing, translation quality estimation, and terminology validation directly inside your active XTM translation projects.

XTM extension on Custom.MT Console

Why XTM Users Choose Custom.MT

full ai automation with XTM icon

Full AI Automation

Run MT, APE, and QE automatically based on workflow steps.

any setup icon

Works With Any XTM Setup

No plugin installation required — the extension connects via callback workflow triggers.

flexible llm and mt engine selection icon

Flexible LLM & MT Engine Selection

Use GPT-4o, GPT-5, Claude, Gemini 2.5 Pro, or your custom MT engines.

secure and compliant icon

Secure & Compliant

EU processing, zero data retention, enterprise-grade credentials.

higher consistency icon

Higher Consistency

Automated steps reduce reviewer workload by 30–60%.

How the XTM Extension Works

The extension is activated through a dedicated Workflow Step + workflowTransitionCallback.

When XTM reaches that step, it sends the content to Custom.MT → the platform runs AI translation, automatic post-editing, quality estimation, and terminology → and returns the translated segments back to XTM.

To configure the Custom.MT side

  • step 1 icon

    Log in to the Custom.MT Console

    Go to Translations → Connections → XTM. This is where the XTM-specific settings live.

  • Add your XTM credentials

    Enter the API key or username/password that XTM will use when sending callback requests. This ensures that Custom.MT can securely authenticate incoming translation jobs.

  • step 3 icon

    Set the callback URL (provided in the Console)

    Custom.MT generates a unique URL that XTM needs to call whenever a workflow step. You copy this URL and provide it to your XTM admin or XTM Support to enable the callback.

  • step 4 icon

    Choose your translation model and workflow

    Select which MT engine or custom model you want to use, and optionally enable Quality Estimation (QE) or Automatic Post-Editing (APE). You can set different models per language pair or per project template.

  • step 5 icon

    Save and test

    Once the connection is activated, move a small test job into the "Custom.MT" workflow step in XTM and check that the translation appears in XTM after processing.

Plans and Prices

Starter Edition

200

monthly

For small translation teams and LSP

Volume included

Features

Note:

The usage of machine translation APIs and GenAI tokens is charged on top of the platform fees. Pricing.

Advanced Edition

1000

monthly

Teams that localize over 10 million target words per year

Volume included

Features

Note:

The usage of machine translation APIs and GenAI tokens is charged on top of the platform fees. Pricing.

Compliance Edition

2500

monthly

Large businesses with compliance requirements

Volume included

Features

Note:

The usage of machine translation APIs and GenAI tokens is charged on top of the platform fees. Pricing.

Frequently Asked Questions

Why would I use the Custom.MT extension with XTM?

The Custom.MT extension lets XTM users automate their entire machine translation pipeline, including MT, custom prompts, APE, and QE, without relying on built-in XTM MT providers. Teams choose the extension because it provides full control over models, flexible workflow automation, and deep customization that XTM alone cannot offer.

Is XTM + Custom.MT a native connector or an extension?

It’s an API-based extension. XTM supports in-product “Custom MT” features and webhook/callback integrations, but the Custom.MT integration works by receiving workflow callbacks from XTM and returning translated segments via API — not by installing a marketplace plugin inside XTM.

Where do I configure the Custom.MT side?

Inside the Custom.MT Console → Translations → Connections → XTM, you enable the XTM connection, provide credentials/API keys for secure calls, and set model/APE/QE preferences.

How do I test the integration once XTM enables callbacks?

Recommended quick test:

  1. Create the special workflow step in XTM (e.g., “CMT Automatic Translation”).
  2. Move a small test project to that step.
  3. Verify that XTM sends the callback, Custom.MT processes the job, and the translated segments return to XTM.
If nothing happens, check callback logs in XTM and request the HTTP/response logs from Custom.MT support. XTM docs explain how to trigger workflows and view project status.
What authentication and security should I expect?

Secure API key or Basic Auth is used for callback authentication (use encrypted password sharing if required). XTM supports webhook secrets and callback configuration; Custom.MT processes in EU infrastructure. Always exchange credentials via secure channels.

What are the main benefits of integrating Custom.MT with XTM?

You get better translation quality, lower post-editing cost, automated workflows, and enterprise-grade security. It’s ideal for teams who want customizable, scalable MT automation inside XTM.