Memsource Legacy API

Memsource Legacy API—API for Editor


Memsource Legacy API will be deprecated in September 2020. It is disabled for all new organization accounts created after May 7th 2019.
Please use Memsource REST API instead.

If you want to use or build your own editor, you can use our API to connect to Memsource. It is highly recommended that you cache your results and optimize your client application in such a way that it does not generate a lot of unnecessary API traffic. For instance, when a user starts scrolling through a file in your workbench without stopping at a specific segment, your workbench should not generate API calls for the segments that the user has just scrolled through. Here are the relevant API calls:

  1. APIs to display segment matches in the CAT Pane:
    - TM segment matches
    - TB segment matches
    - MT segment matches
  2. APIs to retrieve TM/TB search results for the Search Pane:
    - TM search results
    - TB search results
  3. APIs to update TM with new translations and TB with new terms:
    - Uploading an MXLIFF also updates the TM in the write mode
    - Adding new terms

In addition to those mentioned above, there are API calls that are used in Memsource Editor. For instance, API calls that power Quality Assurance, track changes, etc. You will find them in our API Reference article.


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, submit a request to our Support team.
Thank you for your feedback.