Page Summary

outlined_flag

• The Search Ads 360 Reporting API uses a resource-oriented design, where data is organized into collections of resources that can be accessed and manipulated.

• The API primarily uses custom methods likesearch andsearchStream instead of traditional REST methods.

• API endpoints are constructed using an API version prefix, resource name, and method, which are detailed further in linked documentation.

• The guide's examples demonstrate API calls using HTTP, with further instructions available for using thecurl command-line utility.

• Developers should be familiar with Resource Oriented Design and Resource Names before using this API.

This page assumes a familiarity with theResource OrientedDesign andResourceNames developer guides andcomplements them with specific implementation details of the Search Ads 360 Reporting API.

Resource-oriented design

Generally, the Search Ads 360 Reporting API follows a resource-oriented design, modeled ascollections of individually-addressableresources (thenouns of the API).Resources are referenced with their resource names and manipulated using a smallset ofmethods (also known asverbs oroperations).

Theseresource names andmethods, combinedwith a specificAPI version prefix, comprise the URLs of the REST interface.For example, the URL below can be broken down into these individual componentsaccording to the following table:

https://searchads360.googleapis.com/v0/customers/1234567890/searchAds360:search

All REST URLs for a particular version of the API (e.g.,v0)share a common API version prefix. The resource name and method togetheridentifies which API service is being called.

The Search Ads 360 Reporting API makes heavy use ofcustom methods, as opposed to mosttraditional REST APIs that use standard REST methods such aslist andget. The Search Ads 360 Reporting APIincludes two custom methods:search andsearchStream.

The following pages go into more details about the Search Ads 360 Reporting API'sresourcenames,service methods, andJSON naming conventions to illustrate how they're usedtogether to define REST interface endpoints.