(The KantanMT API is currently in BETA I testing – it will be released for wider testing in BETA II over the next two weeks)
The KantanMT API provides existing KantanMT users with a new way to interact with our service as an instant, on-demand translation offering, in addition to the job-based workflow that users have been familiar with to date.
The API leverages innovative technology developed by KantanMT to allow users to translate segments individually and in real-time, but still benefit from the high-quality, secure, and user-controlled translation service that KantanMT customers expect. It uses the existing user client profiles listed on the KantanMT website to serve translations to client applications, so as users train and refine their client profiles over time, the quality of the translations returned by the API will reflect those refinements and allow users to retrieve much higher-quality translations than are possible with competing Machine Translation APIs.
The KantanMT API uses JSON as the messaging format for the responses it serves. JSON is a widely used and highly space-efficient format which enjoys built-in support in some programming languages like PHP and multiple third party parsing and encoding libraries for languages that lack native JSON support such as Java.
Perhaps the biggest benefit of using the API is the scope for completely automating content translation. It is possible to prepare content for translation outside of KantanMT, submit hundreds or thousands of untranslated segments to the API, and perform post-processing on the translated content without any human interaction whatsoever.
However, the API is also well-suited to translating small to medium-sized volumes of content of the order of hundreds of segments. It is also useful when a user only wants to translate selected portions of a document or file rather than uploading all of it as is the case using the website interface. A final example of the API’s usefulness is the situation where a customer wants to review the translated output of individual segments immediately, as they are produced, rather than running a translation job on all the content and then reviewing the translations after the job completes.
Eric Chubb, Senior Software Engineer, KantanMT.com
For more information about KantanMT, or to sign up for trial membership please see www.kantanmt.com