Search Ads 360 Reporting API versi baru kini tersedia. Bergabunglah dengan grup Google searchads-api-announcements untuk terus mendapatkan informasi terbaru tentang peningkatan dan rilis mendatang.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini mengasumsikan bahwa Anda sudah memahami panduan developer Desain Berorientasi Resource dan Nama Resource serta melengkapinya dengan detail implementasi spesifik Search Ads 360 Reporting API.
Desain yang berorientasi pada resource
Umumnya, Search Ads 360 Reporting API mengikuti desain berorientasi resource, yang dimodelkan sebagai koleksiresource yang dapat diberi alamat satu per satu (kata benda API).
Resource dirujuk dengan nama resource-nya dan dimanipulasi menggunakan kumpulan
kecil metode (juga dikenal sebagai kata kerja atau operasi).
Nama resource dan metode ini, yang digabungkan
dengan awalan versi API tertentu, membentuk URL antarmuka REST.
Misalnya, URL di bawah dapat dipecah menjadi setiap komponen ini
sesuai dengan tabel berikut:
Semua URL REST untuk versi API tertentu (misalnya, v0)
memiliki awalan versi API umum. Nama dan metode resource bersama-sama
mengidentifikasi layanan API yang dipanggil.
Search Ads 360 Reporting API banyak menggunakan metode kustom, bukan REST API tradisional yang menggunakan metode REST standar seperti list dan get. Search Ads 360 Reporting API
menyertakan dua metode kustom: search dan searchStream.
Halaman berikut membahas lebih lanjut nama resource, metode layanan, dan konvensi penamaan JSON Search Ads 360 Reporting API untuk mengilustrasikan cara penggunaannya bersama-sama untuk menentukan endpoint antarmuka REST.
[null,null,["Terakhir diperbarui pada 2025-08-29 UTC."],[[["\u003cp\u003eThe Search Ads 360 Reporting API uses a resource-oriented design, where data is organized into collections of resources that can be accessed and manipulated.\u003c/p\u003e\n"],["\u003cp\u003eThe API primarily uses custom methods like \u003ccode\u003esearch\u003c/code\u003e and \u003ccode\u003esearchStream\u003c/code\u003e instead of traditional REST methods.\u003c/p\u003e\n"],["\u003cp\u003eAPI endpoints are constructed using an API version prefix, resource name, and method, which are detailed further in linked documentation.\u003c/p\u003e\n"],["\u003cp\u003eThe guide's examples demonstrate API calls using HTTP, with further instructions available for using the \u003ccode\u003ecurl\u003c/code\u003e command-line utility.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should be familiar with Resource Oriented Design and Resource Names before using this API.\u003c/p\u003e\n"]]],["The Search Ads 360 Reporting API uses a resource-oriented design with collections of resources accessed via resource names. API calls use HTTP protocol and are structured with a version prefix, resource name, and method. This API primarily employs custom methods, specifically `search` and `searchStream`, instead of standard REST methods. URLs are constructed using the version prefix (e.g., `v0`), a resource name, and a method, defining the specific API service. Further details are available on resource names, service methods, and JSON conventions.\n"],null,["# REST Interface Design\n\nThis page assumes a familiarity with the [Resource Oriented\nDesign](https://cloud.google.com/apis/design/resources) and [Resource\nNames](https://cloud.google.com/apis/design/resource_names) developer guides and\ncomplements them with specific implementation details of the Search Ads 360 Reporting API.\n| **Key Point:** The examples throughout this guide use HTTP protocol to demonstrate how to call the API. See the [Examples](/search-ads/reporting/api/reference/rest/examples) page for how you can make these same API calls using the [`curl`](https://curl.haxx.se/) command line utility.\n\nResource-oriented design\n------------------------\n\nGenerally, the Search Ads 360 Reporting API follows a resource-oriented design, modeled as\n*collections* of individually-addressable *resources* (the *nouns* of the API).\nResources are referenced with their resource names and manipulated using a small\nset of *methods* (also known as *verbs* or *operations*).\n\nThese [resource names](/search-ads/reporting/api/reference/rest/resource-names) and [methods](/search-ads/reporting/api/reference/rest/service-methods), combined\nwith a specific *API version prefix*, comprise the URLs of the REST interface.\nFor example, the URL below can be broken down into these individual components\naccording to the following table: \n\n https://searchads360.googleapis.com/v0/customers/1234567890/searchAds360:search\n\n| API Version Prefix | Resource Name (relative) | Method |\n|------------------------------------------|--------------------------|----------|\n| `https://searchads360.googleapis.com/v0` | `customers/1234567890` | `search` |\n\nAll REST URLs for a particular version of the API (e.g., `v0`)\nshare a common API version prefix. The resource name and method together\nidentifies which API service is being called.\n\nThe Search Ads 360 Reporting API makes heavy use of *custom methods* , as opposed to most\ntraditional REST APIs that use standard REST methods such as `list` and `get`. The Search Ads 360 Reporting API\nincludes two custom methods: `search` and `searchStream`.\n\nThe following pages go into more details about the Search Ads 360 Reporting API's [resource\nnames](/search-ads/reporting/api/reference/rest/resource-names), [service methods](/search-ads/reporting/api/reference/rest/service-methods), and\n[JSON naming conventions](/search-ads/reporting/api/reference/rest/json-mappings) to illustrate how they're used\ntogether to define REST interface endpoints."]]
