An API is like a direct link between your website and Gengo. It’s not a browser plugin like Flash, it’s a system-level connection. It allows your site to order translations directly, without requiring manual input.
Your website might already use other APIs for:
Loading maps (like Google Maps) onto your pages
Getting live stock quotes from a service like Yahoo!
Pulling in Tweets or external news data
Connecting to a payment provider (credit card processor) or PayPal
How might your website use the API?
If you publish a blog, your website might use the API to send Gengo the text to be translated - the moment you hit the ‘Publish’ button.
If you have an e-commerce site, your website might use the API to send Gengo the product descriptions you create to be translated.
If you have a customer support system, you might use the API to automatically send foreign-language emails to be translated at Gengo.
If you run an intranet, the articles your co-workers publish could be sent for translation automatically the moment they publish them.
Why should we bother connecting to the API?
Connecting to the API will save your company time and money by removing manual labour. It allows you to get content translated within your existing systems - rather than having to copy and paste text into an order form or constantly email translators to get things done. Because of this efficiency, you can offer far more content (translated at high quality) in foreign languages, and attract more users.
Still not sure?
Send your development team a link to this page [ http://gengo.com/api/ ]. They will understand the concept of an API connecting your application to Gengo, and can help you decide how to proceed.