For years Language I/O (LIO) has offered turnkey multilingual customer support software solutions for companies that work within LIO supported customer relationship management (CRM) systems such as Zendesk, Salesforce and Oracle. However, with the growing trend toward APIs (application programming interfaces), we now offer an API for translation.
What Is An API?
An API is a way for any developer to hit and then use a technology service in a way that integrates the output of that service directly into the developer’s software. In LIO’s case, having an API means that companies who are not using one of our support CRMs can still hit our proprietary core technology, which provides accurate real-time translation for company-specific content. Essentially, having an API lets all apps talk to each other.
What Should a Translation API Include?
A translation API should include the following:
An Adherence to REST Principles
LIO’s API follows REST (Representational State Transfer) principles, which are guidelines for creating APIs that help both the provider of the API and the user to have a seamless integration. REST principles include ensuring uniform interface; client-server separation; layer independence; caching; and stateless transfer.
A Commitment to Security
Security breaches of any type are brutal. When looking for a translation API, make sure the company you’re vetting takes security seriously. LIO never stores PII (personally identifiable information), is GDPR compliant and ISO 27001 certified.
The Ability to Filter Data
APIs that are developer friendly typically include an ability to easily filter data. This allows developers to locate the information they need to make the best use of the API.
Clear, Accurate Documentation
The documentation that a developer receives to implement the API serves as a guidebook. When looking for a translation API, the API documentation should be well organized and accurate.
If you’re interested in LIO’s documentation, please contact us.