Memsource REST API

REST API Overview

Memsource offers a set of API calls which allow for:

  • Integration of Memsource and any third party software (translation management tools, CMSs, etc.)

  • Development of a translator's workbench. Memsource Editor is built on top of public APIs.

  • Creation of a brand new tool or service which uses Memsource in its backend.

Developer Edition

To start using Memsource REST APIs, sign up for the Memsource Developer edition. This free edition is designed to be used as a sandbox for API development. Users can use Postman to learn about and test Memsource APIs.

Developer edition restrictions:

Developers may use this edition for development and testing purposes only. Contact Memsource Technical Support if you need these limits increased or modified.

  • A maximum of 2 translation jobs stored at any time

  • A maximum of 1 MB for job file sizes

  • A maximum of 1 Administrator user and 1 Linguist user

Memsource REST API documentation is available on a dedicated site. It is automatically generated and can be downloaded and exported.

Basic Workflow

Memsource procedures and workflow must be understood before using Memsource APIs. It is recommended to be familiar with a procedure in the Memsource application before implementing the related API.

The basic workflow is:

  1. Create a TM, TB, and optionally, add a machine translation engine.

  2. Create a project with the TM/TB/machine translation engine attached (if needed).

  3. Upload your file for translation to the project (also called creating a job in Memsource).

  4. You can then analyze, pre-translate or assign the job to a Linguist.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question you can leave a public comment below or Submit a request to our Support team.
Thank you for your feedback.

Comments

0 comments

Article is closed for comments.