Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A API Google Ads pode ser chamada usando gRPC ou REST. As duas
interfaces expõem um design voltado a recursos
compartilhado com outras APIs do Google Cloud.
Recomendamos usar as bibliotecas de cliente oficiais do Google sempre que possível. Elas fornecem código idiomático e seguro para cada tipo de linguagem
e processam muitos detalhes de baixo nível de comunicação com a API, como
configurações de tempo limite, paginação do conjunto de resultados e
autenticação. Nossas bibliotecas de cliente também incluem um
amplo conjunto de exemplos de código e utilitários que ajudam em
tarefas comuns, como criar
nomes de recursos e processar
máscaras de campo.
Neste guia, apresentamos detalhes específicos do REST e explicamos o que você precisa saber para chamar a interface REST diretamente, sem usar uma biblioteca de cliente compatível com o Google. Este guia pode ser útil se você estiver escrevendo seu próprio código personalizado para usar o REST diretamente ou usar uma biblioteca de cliente HTTP de terceiros.
[null,null,["Última atualização 2025-08-27 UTC."],[[["\u003cp\u003eGoogle Ads API can be accessed using either gRPC or REST, with gRPC being the recommended method for interacting with the API.\u003c/p\u003e\n"],["\u003cp\u003eOfficial Google client libraries, built on gRPC (except for Perl which uses REST), are strongly encouraged for ease of use and handling low-level communication details.\u003c/p\u003e\n"],["\u003cp\u003eThis guide focuses on using the REST interface directly, primarily for users building custom solutions or using third-party HTTP client libraries.\u003c/p\u003e\n"],["\u003cp\u003eClient libraries provide benefits like idiomatic code, type safety, pagination handling, authentication, and access to code examples and utilities for common tasks.\u003c/p\u003e\n"]]],["The Google Ads API utilizes gRPC or REST interfaces, sharing a resource-oriented design. Using Google's client libraries is highly recommended for type-safe code, handling communication details like timeouts, pagination, and authentication. The official client libraries use gRPC, except for the Perl library, which uses REST. This guide details using REST directly without client libraries, useful for custom code or third-party HTTP clients. It focuses on information outside of what the official client libraries cover.\n"],null,["# REST Interface\n\n| **Key Point:** We strongly recommend using our [official client\n| libraries](/google-ads/api/docs/client-libs) wherever you can. All Google provided client libraries are implemented using gRPC, except for the [Perl\n| library](https://github.com/googleads/google-ads-perl/), which uses the REST interface. Unless you are specifically looking for details about REST, consult the [gRPC documentation](/google-ads/api/reference/rpc) for reference documentation that covers our official client libraries.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThe Google Ads API can be called either using [gRPC](//grpc.io/) or REST. Both\ninterfaces expose a [resource-oriented design](//cloud.google.com/apis/design)\nshared with other Google Cloud APIs.\n\nWe recommend using Google's official [client libraries](/google-ads/api/docs/client-libs)\nwherever possible. They provide idiomatic, type-safe code in each supported\nlanguage and handle many low-level details of communication with the API (like\ntimeout settings, result set [pagination](/google-ads/api/rest/examples#paginated), and\n[authentication](/google-ads/api/rest/auth)). Our client libraries also include an\nextensive set of [code examples](/google-ads/api/docs/samples) and utilities that assist with\ncommon tasks, such as constructing\n[resource names](/google-ads/api/rest/design/resource-names) and handling\n[field masks](/google-ads/api/rest/common/mutate#update).\n\nThis guide presents details specific to REST and explains what you need to know\nto call the REST interface directly, without the use of a Google-supported\nclient library. This guide may be useful if you are writing your own custom code\nto use REST directly or using a third-party HTTP client library."]]
