The design of the Google Ads API differs from a traditional REST architecture
because it primarily uses custom methods, such as
of the more traditional
These actions are expressed in REST URLs by using the HTTP mapping
convention of a
: to separate the custom verb from the rest of the URL.
For example, a campaign mutate API call uses the following URL:
One reason that the API uses custom methods is to enable batching of multiple
operations into a single API request. Strict REST semantics would only allow
updating one campaign at a time. A traditional REST
update to a
campaign, for example, would require sending one HTTP PATCH request per campaign
To allow many operations to be bundled together within a single request body,
the Google Ads API instead defines a custom
mutate method for most resources.
Similarly, to enable batch reads (fetching many objects at once) from the API,
the API uses a custom
search method with a SQL-like Google Ads Query
The Common methods page goes into detail on the most frequently used methods in the Google Ads API.