Stay organized with collections
Save and categorize content based on your preferences.
API usage overview
This guide provides an overview of using the Cloud Translation API and its
reference documentation.
Client libraries, REST, and gRPC
You can access the API through client libraries, REST, or gRPC
(Cloud Translation - Advanced only).
Client libraries
Google provides client libraries for many popular languages to access the APIs.
If your desired programming language is supported by the client libraries, we
recommend that you use this option.
Simple JSON interface.
Well supported by many Google and third-party tools and libraries.
You must build your own client.
You must
implement authentication.
You must implement retries.
Less efficient JSON HTTP request body.
gRPC
Cloud Translation - Advanced supports
gRPC. For more
information, see the RPC reference,
which provides a generic description of the types, methods, and fields generated
for a gRPC library.
You must generate your own client from Google-supplied protocol buffers.
You must
implement authentication.
You must implement retries.
Type, method, and field names
Depending on whether you are using client libraries, REST, or gRPC, the type,
method, and field names for the API vary:
REST is arranged by resource hierarchies and their methods.
Client libraries and gRPC are arranged by services and their methods.
REST field names use camel case, though the API service will accept either
camel case or snake case.
gRPC field names use snake case.
Client library field names use either title case, camel case or snake case,
depending on which name is idiomatic for the language.
API editions
Cloud Translation offers two editions: Basic (v2) and Advanced (v3). Each edition
has its own set of APIs and capabilities. For more information, see the
Editions page.
What's next
For more information about using client libraries or REST, see get started
translating text with v3 or
v2.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# API usage overview\n==================\n\nThis guide provides an overview of using the Cloud Translation API and its\nreference documentation.\n\nClient libraries, REST, and gRPC\n--------------------------------\n\nYou can access the API through client libraries, REST, or gRPC\n(Cloud Translation - Advanced only).\n\n### Client libraries\n\nGoogle provides client libraries for many popular languages to access the APIs.\nIf your desired programming language is supported by the client libraries, we\nrecommend that you use this option.\n\n- Cloud Translation - Basic [client\n libraries](/translate/docs/reference/libraries/v2/overview-v2)\n- Cloud Translation - Advanced [client\n libraries](/translate/docs/reference/libraries/v3/overview-v3)\n\n### REST\n\nThe Cloud Translation API supports [REST](https://wikipedia.org/wiki/Representational_state_transfer).\n\n- Cloud Translation - Basic [translate text method](/translate/docs/reference/rest/v2/translate)\n- Cloud Translation - Advanced [overview](/translate/docs/reference/rest).\n\n### gRPC\n\nCloud Translation - Advanced supports\n[gRPC](https://grpc.io/). For more\ninformation, see the [RPC reference](/translate/docs/reference/rpc),\nwhich provides a generic description of the types, methods, and fields generated\nfor a gRPC library.\n\nType, method, and field names\n-----------------------------\n\nDepending on whether you are using client libraries, REST, or gRPC, the type,\nmethod, and field names for the API vary:\n\n- REST is arranged by resource hierarchies and their methods.\n- Client libraries and gRPC are arranged by services and their methods.\n- REST field names use camel case, though the API service will accept either camel case or snake case.\n- gRPC field names use snake case.\n- Client library field names use either title case, camel case or snake case, depending on which name is idiomatic for the language.\n\nAPI editions\n------------\n\nCloud Translation offers two editions: Basic (v2) and Advanced (v3). Each edition\nhas its own set of APIs and capabilities. For more information, see the\n[Editions](/translate/docs/editions) page.\n\nWhat's next\n-----------\n\n- For more information about using client libraries or REST, see get started translating text with [v3](/translate/docs/advanced/translate-text-advance) or [v2](/translate/docs/basic/translate-text-basic)."]]