KantanMT Connector: Difference between revisions
Jump to navigation
Jump to search
m (1 revision imported) |
|||
| Line 2: | Line 2: | ||
__TOC__ | __TOC__ | ||
==Overview== | ==Overview== | ||
{{WarningBox|This service is not to be use after May 31st 2018.<br/> | |||
Instead, please use the [[KantanMT v2.1 Connector]].}} | |||
The commercial [https://kantanmt.com KantanMT] service can be accessed via API, which is documented at http://docs.kantanmt.apiary.io. | The commercial [https://kantanmt.com KantanMT] service can be accessed via API, which is documented at http://docs.kantanmt.apiary.io. | ||
Latest revision as of 17:36, 1 April 2018
Overview
Warning: This service is not to be use after May 31st 2018.
Instead, please use the KantanMT v2.1 Connector.
Instead, please use the KantanMT v2.1 Connector.
The commercial KantanMT service can be accessed via API, which is documented at http://docs.kantanmt.apiary.io.
The connector assumes that the specified KantanMT engine is running, which is not always the case. Users must start the the appropriate engine prior to using the connector, either via the KantanMT dashboard or using the API (for example, with curl.)
Using the Connector
In Rainbow, the connector can be accessed through the Leveraging Step. It can also be called programmatically.
Parameters
KantanMT Client Profile (internal name: profileName) — the client profile to use. (Sample value: "Test-EN-DE")
KantanMT Authorization Token (internal name: apiToken) — the authorization token. (Sample value: "ABCdef123467")
Limitations
- The connector assumes that the specified KantanMT engine is running, which is not always the case. Users must start the the appropriate engine prior to using the connector, either via the KantanMT dashboard or using the API (for example, with curl.)