Google Ads API는 gRPC 또는 REST를 사용하여 호출할 수 있습니다. 두 인터페이스 모두 다른 Google Cloud API와 공유되는 리소스 중심 설계를 노출합니다.
가능한 경우 Google의 공식 클라이언트 라이브러리를 사용하는 것이 좋습니다. 지원되는 각 언어로 관용적이고 유형 안전 코드를 제공하고 API와의 통신에 관한 하위 수준 세부정보 (예: 시간 제한 설정, 결과 집합 페이지로 나누기, 인증)를 처리합니다. 클라이언트 라이브러리에는 리소스 이름 구성 및 필드 마스크 처리와 같은 일반적인 작업을 지원하는 광범위한 코드 예제 및 유틸리티도 포함되어 있습니다.
이 가이드에서는 REST 관련 세부정보를 제공하고 Google에서 지원하는 클라이언트 라이브러리를 사용하지 않고 REST 인터페이스를 직접 호출하기 위해 알아야 할 사항을 설명합니다. 이 가이드는 REST를 직접 사용하기 위해 커스텀 코드를 작성하거나 서드 파티 HTTP 클라이언트 라이브러리를 사용하는 경우에 유용할 수 있습니다.
[null,null,["최종 업데이트: 2025-09-05(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."]]
