The REST interface overview

AI-generated Key Takeaways

outlined_flag

• We strongly recommend using the official client libraries, which are implemented using gRPC except for the Perl library.

• The Google Ads API supports calls via either gRPC or REST interfaces, both utilizing a resource-oriented design.

• Official client libraries are recommended for their idiomatic, type-safe code and handling of low-level communication details.

• This guide specifically details how to call the REST interface directly without using a Google-supported client library.

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.