Edit: Memsource Legacy APIs will be supported until 30 September 2020, after which only REST APIs will be supported.
APIs have always been one of the strongest features of the Memsource platform. Many global companies and translation agencies have used them since the earliest days of Memsource to connect and customize the platform for their localization needs.
Webinar: Faster Data Transfer with REST APIs Wednesday, October 25, 2017, 17:00 CEST
API Usage in Memsource
With the advancement of technology and an ever-increasing number of connectors and integrations, APIs are being used more and more by Memsource users to customize the system according to their policies or specific workflows. Over the past two years, API usage in Memsource Cloud has increased from around 30,000,000 monthly calls to between an average of 40,000,000-50,000,000 monthly calls.
Additionally, the Memsource platform uses the same APIs it offers to its clients. This allows us to ensure the highest quality data transfers are utilized and encourages us to constantly develop and improve it for our clients. Within Memsource, APIs are used in Memsource, both web and desktop editors, and the new mobile app.
In response to the increasing use, the desire for ever-increasing data speeds, and a drive to provide the best connections possible, the Memsource API team is developing new REST APIs for all users with API-enabled editions. A few have been released and the rest will come over the following weeks. Edit: As of January 16, 2018, all REST APIs are now available.
A Chat with the API Team
The Memsource Marketing team loves talking about localization technology, but we needed some reinforcement for this post. We spoke with developer Jiří Zmeškal and the rest of the API team about what this means for current Memsource users and developers who wish to take advantage of the new API technology and documentation format.
What is a REST API?
A REST - or Representational state transfer - API is a way to enable interoperability between computer systems using HTTP protocol. It uses HTTP methods such as GET, POST, PUT, DELETE and PATCH. (These are types of operations to achieve a desired action. For example, if you enter a URL into a web browser address bar, the browser will carry out an HTTP GET request to the URL.)
What is the difference between the previous Memsource APIs and the new REST-based APIs?
The main difference between them is their format. The previous APIs are parameter-based while the new APIs are based on JSON. Using both JSON and standard HTTP allows greater flexibility - with JSON you can perform more complex requests, faster.
We’ve released a few new APIs in our new documentation and the rest will come in the upcoming weeks.
What were the reasons for doing an update? What are the benefits?
We wanted to make our APIs more user-friendly and provide a more common API standard for developers. We know that a lot of developers are used to working with REST, so our update makes it easier for them to integrate our APIs.
Some additional benefits include:
- User-friendly documentation: We wanted to make the API documentation easier to use - we have done this by incorporating the OpenAPI (previously Swagger) specification. The API documentation is also automatically generated and can even be downloaded and exported.
- Faster response times: Users will notice improvements such as faster response times as requests are processed more quickly.
Ok, what about the nuts and bolts - how is the new REST API built differently? The structure of our new APIs is more effective. We have:
- Reduced the response size: The previous APIs returned too much information. We have reduced the size by looking at both requests and responses in our previous APIs.
- Created a standard set of operations: Each new API includes the list, get, create, update and delete operations.
- Improved HTTP methods: HTTP GET can now be used for creating a list or retrieving details about a resource without changing the state of the resource. HTTP PUT is now available so it’s possible to do a complete update of a resource.
- Included more HTTP headers: The new API can use more headers, including the ‘Accept’ header which allows users to specify the format of the answer they require from the HTTP call.
You’ve made some updates to the API documentation - what are some of those changes? Previously, a request body would need to be created from scratch by a user. Now, our documentation provides API request and response samples which can be easily copied.
Users can now download the documentation in a machine-readable format (JSON or YAML) and import it into tools such as Postman and Swagger Editor. The documentation also includes access to third-party libraries which users can use to generate code.
Will I have to change anything in my Memsource account? No, your Memsource account is not affected and you don’t need to set up a new API. As long as you have access to a Memsource edition that supports API calls, you can benefit from the new ones. Also, the new APIs won’t affect any existing integrations.
Can I still use the previous Memsource API?
No, the previous Memsource APIs will be supported until 30 September 2020.
Try Memsource Today
Want to test out the new REST APIs for yourself? Start a free trial.