Release Notes

This page documents production updates to Cloud Translation API. We recommend that Cloud Translation API developers periodically check this list for any new announcements. Major changes will also be announced via the cloud-translate-discuss mailing list.

June 19, 2017

The Cloud Translation API no longer supports conditional HTTPS requests. If-Match, If-None-Match, or ETag headers in requests to the Cloud Translation API are ignored. The Cloud Translation API returns a status code of 200 for successful requests, but does not return a status code of 304 for conditional HTTPS requests. Conditional HTTPS requests are billed as a normal request to the Cloud Translation API.

The https://www.googleapis.com/language/translate/v2 endpoint now supports the Neural Machine Translation (NMT) model. However, we recommend that you use the https://translation.googleapis.com/language/translate/v2 endpoint for requests to the Cloud Translation API.

April 6, 2017

The Google Cloud Translation API is no longer taking requests for access to the Premium Edition (Beta). Instead, the premium features of the Google Cloud Translation API have been made generally available in the Standard Edition.

You now have access to the robust translation features available using the Neural Machine Translation (NMT) model. There is no difference in pricing between the standard, Phrase-Based Machine Translation (PBMT) model, and the NMT model.

By default, when you make a translation request to the Google Cloud Translation API, your text is translated using the NMT model. If the NMT model is not supported for the requested language translation pair, or if you explicitly request it, the PBMT model is used.

In order for your request to be translated using the NMT model, you must send your request to the current Translation API endpoint: https://translation.googleapis.com/language/translate/v2. The https://www.googleapis.com/language/translate/v2 endpoint does not support the NMT model.

NMT models are computationally intensive and may take more time to translate your query as compared to the same query translated using the PBMT model. If your application is latency sensitive, we recommend that you try both models to determine which best fits your needs for response time.

The model query parameter has been added to the translate method. You can use the model parameter to explicitly specify the translation model for your request. Specify base to use the PBMT model, and nmt to use the NMT model.

If you do not specify a model parameter for your request, then nmt is used.

If you specify the nmt model, and the requested language translation pair is not supported for the NMT model, then the request is translated using the base model.

November 15, 2016

Changed API endpoint from www.googleapis.com to translation.googleapis.com.

API endpoint of www.googleapis.com will continue to work, but migrate code to translation.googleapis.com to take advantage of the latest features.

Send feedback about...

Translation API