Cloud Translation: Node.js Client
TheCloud Translation API,can dynamically translate text between thousandsof language pairs. The Cloud Translation API lets websites and programsintegrate with the translation service programmatically. The Cloud TranslationAPI is part of the larger Cloud Machine Learning API family.
A comprehensive list of changes in each version may be found inthe CHANGELOG.
- Cloud Translation Node.js Client API Reference
- Cloud Translation Documentation
- github.com/googleapis/nodejs-translate
Read more about the client libraries for Cloud APIs, including the olderGoogle APIs Client Libraries, inClient Libraries Explained.
Table of contents:
Quickstart
Before you begin
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Cloud Translation API.
- Set up authentication with a service account so you can access theAPI from your local workstation.
Installing the client library
npm install @google-cloud/translateUsing the client library
/** * TODO(developer): Uncomment the following line before running the sample. */// const projectId = 'YOUR_PROJECT_ID';// Imports the Google Cloud client libraryconst {Translate} = require('@google-cloud/translate').v2;// Instantiates a clientconst translate = newTranslate({projectId});async function quickStart() { // The text to translate const text = 'Hello, world!'; // The target language const target = 'ru'; // Translates some text into Russian const [translation] = awaittranslate.translate(text, target); console.log(`Text: ${text}`); console.log(`Translation: ${translation}`);}quickStart();Samples
Samples are in thesamples/ directory. Each sample'sREADME.md has instructions for running its sample.
| Sample | Source Code | Try it |
|---|---|---|
| Hybrid Glossaries | source code | ![]() |
| Quickstart | source code | ![]() |
| Translate | source code | ![]() |
TheCloud Translation Node.js Client API Reference documentationalso contains samples.
Supported Node.js Versions
Our client libraries follow theNode.js release schedule.Libraries are compatible with all currentactive andmaintenance versions ofNode.js.
Client libraries targeting some end-of-life versions of Node.js are available, andcan be installed via npmdist-tags.The dist-tags follow the naming conventionlegacy-(version).
Legacy Node.js versions are supported as a best effort:
- Legacy versions will not be tested in continuous integration.
- Some security patches may not be able to be backported.
- Dependencies will not be kept up-to-date, and features will not be backported.
Legacy tags available
legacy-8: install client libraries from this dist-tag for versionscompatible with Node.js 8.
Versioning
This library followsSemantic Versioning.
This library is considered to beGeneral Availability (GA). This means itis stable; the code surface will not change in backwards-incompatible waysunless absolutely necessary (e.g. because of critical security issues) or withan extensive deprecation period. Issues and requests againstGA librariesare addressed with the highest priority.
More Information:Google Cloud Platform Launch Stages
Contributing
Contributions welcome! See theContributing Guide.
Please note that thisREADME.md, thesamples/README.md,and a variety of configuration files in this repository (including.nycrc andtsconfig.json)are generated from a central template. To edit one of these files, make an editto its template in thisdirectory.
License
Apache Version 2.0
SeeLICENSE
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-12 UTC.
