您可以使用 gRPC 或 REST 呼叫 Google Ads API。這兩個介面都會公開與其他 Google Cloud API 共用的資源導向設計。
建議您盡可能使用 Google 官方的用戶端程式庫。這些程式碼會以各種支援語言提供符合類型、安全無虞的安全程式碼,並處理許多與 API 之間的低階詳細資料 (例如逾時設定、結果集 pagination 和驗證)。我們的用戶端程式庫還包含一系列程式碼範例和公用程式,可協助處理一般工作,例如建構資源名稱和處理欄位遮罩。
本指南提供 REST 專屬的詳細資訊,並說明必須直接呼叫的 REST 介面,而不使用 Google 支援的用戶端程式庫。如果您要編寫自己的自訂程式碼以直接使用 REST,或使用第三方 HTTP 用戶端程式庫,本指南可能很有幫助。
[null,null,["上次更新時間:2025-08-27 (世界標準時間)。"],[[["\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."]]