Stay organized with collections
Save and categorize content based on your preferences.
The Google Ads API can be called either using gRPC or REST. Both
interfaces expose a resource-oriented design
shared with other Google Cloud APIs.
We recommend using Google's official client libraries
wherever possible. They provide idiomatic, type-safe code in each supported
language and handle many low-level details of communication with the API (like
timeout settings, result set pagination, and
authentication). Our client libraries also include an
extensive set of code examples and utilities that assist with
common tasks, such as constructing
resource names and handling
field masks.
This guide presents details specific to REST and explains what you need to know
to call the REST interface directly, without the use of a Google-supported
client library. This guide may be useful if you are writing your own custom code
to use REST directly or using a third-party HTTP client library.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-10 UTC."],[],["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,[]]
