Google Search Ads 360 Reporting API

Name: Search Ads 360 Reporting API
Brand: Search Ads 360 Reporting API
Availability: InStock

✓ Official Vendor SpecMarketingAdvertisingoauth25 Endpoints

Install Jentic One Beta

Connect the Search Ads 360 Reporting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Search Ads 360 Reporting API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Search Ads 360 Reporting API.

Run a Search Ads 360 reporting query against a customer with a SQL-like select statement

List accessible customers visible to the calling OAuth principal

Enumerate custom columns defined for a given customer

GET STARTED

Start building with Search Ads 360 Reporting API

Explore with Jentic

View OpenAPI Document

For Agents

Run Search Ads 360 reporting queries - search rows of campaign, ad group, and conversion metrics, list accessible customers, and retrieve resource metadata for query authoring.

Use for: Run a SearchAds360 query for last week's campaign spend across all customers, List all accessible customers under my login customer ID, Get the custom columns defined on a specific Search Ads 360 customer, Retrieve the resource metadata for the campaign resource

Not supported: Does not edit campaigns, upload conversions, or change bid strategies - use for retrieving Search Ads 360 reporting data and metadata only.

Use Cases

Patterns agents use Search Ads 360 Reporting API for, with concrete tasks.

★ Daily marketing performance ETL

An ETL agent pulls daily Search Ads 360 metrics - impressions, clicks, conversions, cost - into the marketing data warehouse. It calls the search endpoint with a SearchAds360 query selecting the desired fields, paginates through results, and writes them to the warehouse for dashboards. The query language matches Google Ads GAQL closely, so existing knowledge transfers.

POST /v0/customers/{+customerId}/searchAds360:search with query 'SELECT campaign.id, metrics.impressions FROM campaign WHERE segments.date DURING LAST_7_DAYS'.

Multi-customer rollup reporting

Agencies operating multiple Search Ads 360 customers need rollup reports. An agent calls listAccessibleCustomers, iterates each customer ID, and runs the same query against each, aggregating results into a single performance summary. The login-customer-id header lets the call run under the agency's manager account.

GET /v0/customers:listAccessibleCustomers, then call /v0/customers/{customerId}/searchAds360:search per ID with the same query.

Custom column inspection

Marketing operations teams maintain custom columns such as ROAS targets per advertiser. An agent enumerates customColumns for each customer, validates that the expected columns exist, and surfaces drift to ops. This protects downstream reports from silently breaking when custom columns are renamed.

GET /v0/customers/{+customerId}/customColumns and compare the returned list to the team's expected definition.

Agent-driven ads reporting through Jentic

An AI agent built on Jentic answers ad-hoc questions about Search Ads 360 performance: spend by campaign, conversion rate by device. It searches Jentic for the right operation by intent, runs the query, and summarises the result. OAuth tokens stay isolated in your Jentic One instance.

Search Jentic for 'run search ads 360 query', execute /v0/customers/{customerId}/searchAds360:search with the user's natural-language-derived query.

Key Endpoints

5 endpoints — the search ads 360 reporting api automates the download of search marketing reports from google's enterprise search-ads management product.

METHOD

PATH

DESCRIPTION

POST

/v0/customers/{+customerId}/searchAds360:search

Run a SearchAds360 reporting query

GET

/v0/customers:listAccessibleCustomers

List customers accessible to the principal

GET

/v0/customers/{+customerId}/customColumns

List custom columns defined for a customer

POST

/v0/searchAds360Fields:search

Search the metadata schema for query authoring

GET

/v0/{+resourceName}

Retrieve a single resource record by name

POST

/v0/customers/{+customerId}/searchAds360:search

Run a SearchAds360 reporting query

GET

/v0/customers:listAccessibleCustomers

List customers accessible to the principal

GET

/v0/customers/{+customerId}/customColumns

List custom columns defined for a customer

POST

/v0/searchAds360Fields:search

Search the metadata schema for query authoring

GET

/v0/{+resourceName}

Retrieve a single resource record by name

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run a Search Ads 360 query' or 'list accessible customers', and Jentic returns the matching v0 operation with its input schema so the agent calls the right endpoint without reading the SA360 reporting docs.

Time to first call

FAQs

Specific to using Search Ads 360 Reporting API through Jentic.

What authentication does the Search Ads 360 Reporting API use?

It uses Google OAuth 2.0 with the doubleclicksearch scope, declared as Oauth2 and Oauth2c. Calls running under a manager account also pass a login-customer-id header. Through Jentic, OAuth credentials are held encrypted in the vault and exchanged for short-lived access tokens at execution time.

Can I run reporting queries with the SearchAds360 API?

Yes. POST /v0/customers/{+customerId}/searchAds360:search accepts a SearchAds360 query language statement - for example 'SELECT campaign.id, metrics.clicks FROM campaign WHERE segments.date DURING LAST_30_DAYS' - and returns paginated rows. The endpoint supports a pageSize parameter for bounded fetches.

What are the rate limits for the Search Ads 360 Reporting API?

Google enforces per-customer rate limits on SearchAds360 reporting; the published default is 4,800 operations per day per customer, with concurrent request limits per developer token. Pagination must use the next_page_token returned by the search endpoint to avoid duplicating row consumption against the quota.

How do I run a Search Ads 360 query through Jentic?

Search Jentic for 'run search ads 360 query', load the schema for POST /v0/customers/{+customerId}/searchAds360:search, and execute with the customerId and query string. Jentic returns the parsed rows so the agent can summarise or write them to a warehouse.

Is the Search Ads 360 Reporting API free?

The reporting API is included with Search Ads 360 entitlement; there is no separate per-call charge from Google. Costs accrue only against the Search Ads 360 product license under the customer's commercial agreement with Google.

How do I list which customers I can access?

Call GET /v0/customers:listAccessibleCustomers with the OAuth credentials of the calling user and the login-customer-id header set to the manager account if applicable. The endpoint returns the resource names of every accessible customer, which can then be passed into reporting queries.

Can I limit what my agent is allowed to do with the Search Ads 360 Reporting API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API carries the customer id in the URL path (/v0/customers/{+customerId}/searchAds360:search), so a rule can pin the agent to a single customer. You can allow it to run reporting queries, list custom columns, and enumerate accessible customers while blocking everything else. Since these endpoints only retrieve reporting data and metadata, the agent cannot edit campaigns, upload conversions, or change bid strategies. The stored OAuth credential is injected at execution time and never enters the agent's prompt or logs.

Google Search Ads 360 Reporting API

Connect the Search Ads 360 Reporting API to your agent

Capabilities

Start building with Search Ads 360 Reporting API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs