Mansa Platform Docs
Console

Phrase TMS

Connect Phrase TMS (Language AI) to Mansa as a bring-your-own (BYO) machine translation engine. Phrase calls Mansa over HTTPS; usage is billed to your Mansa Credits balance.

Prerequisites

  • A Mansa account with a funded Mansa Credits balance
  • A Mansa API key (msk_live_… or legacy MT_API…) stored on your server
  • Phrase TMS access with permission to manage Language AI and MT profiles

Connector settings

In Phrase, open TMS → Language AI → MT profiles, add a BYO Engine, and use:

FieldValue
Base engine URLhttps://api.mymansa.ai/v1/integrations/phrase
Authorization header nameX-Api-Token
Authorization tokenYour Mansa API key

Authorization: Bearer <MANSA_API_KEY> also works if your Phrase configuration accepts a Bearer header instead of X-Api-Token.

After entering credentials, run Validate connection in Phrase. All checks should pass before you save the profile.

MT profile setup

  1. In Phrase TMS, go to Language AI → MT profiles.
  2. Click Add profile, then Add engines.
  3. Choose BYO Engine and enter the connector settings above.
  4. Click Validate connection, then Add to save the engine to the profile.
  5. Assign the profile to the language pairs you need in Phrase.

Phrase Portal (optional)

To expose Mansa through Phrase Portal for reviewers or external users:

  1. In Phrase Portal, add the Mansa add-on (or your custom portal using the MT profile).
  2. Under General settings, select the Mansa MT profile you created.
  3. Configure languages, resources, quality options, and access rules, then save and share the portal link.

Supported locales

Phrase sends BCP-47-style locale codes. Mansa supports the same language catalog as Translate, including:

en, sw, ar, af, am, ha, ig, so, xh, zu, yo, rw, sn, tn, ny, lg, mg, om, st, nso, ts, rn, nr, ss, ti, tw, ak, ee, ln, kg, bm, bem

Beta locales (tw, ak, ee, ln, kg, bm, bem, and related pairs) are primarily available between English and the beta language.

Limits

  • Up to 500 segments per Phrase sync or async translate request
  • Async jobs: poll with Phrase’s usual async status and result endpoints on the same base URL

Billing

Phrase connector traffic debits Mansa Credits on your Mansa account (same per-character translation rate as Translate). Manage keys and balances in the Mansa console.

Troubleshooting

HTTP statusMeaning
401Missing or invalid Mansa API key in X-Api-Token or Authorization
402Insufficient Mansa Credits
422Invalid segments or translation failure for one or more segments
503Translation service temporarily unavailable — retry after a short delay

Phrase error bodies use { "error": "…" } rather than the RFC 7807 shape used by other /v1 JSON endpoints.