List negative keywords
The queries you have blocked, at campaign and/or ad-group level. Negatives carry no metrics, so an over-blocking negative is only findable here — and this is the only endpoint that returns the keywordId a removal needs. Negatives count toward the 5,000-per-campaign and 5,000-per-ad-group caps.
Required scope: read.
Authorization
bearerAuth An API key from Workspace → Settings → API keys, sent as Authorization: Bearer tsk_….
Authorization has two independent axes.
The scope is ranked — a key satisfies any requirement at or below its own tier:
read— see state. Never changes anything.write— propose changes (theactions/*endpoints), trigger audits and reports.admin— connection, account import, sync, targets and brief.
There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.
The approval grant (can_approve) is a separate boolean, not a rung. Deciding a queued proposal — approve, reject, revert — needs write and the grant. Keeping them on separate axes is what makes the review gate a control rather than a convention: a key that may propose is not automatically a key that may approve its own proposal.
A key is either org-scoped (reaches every account, optionally limited to a subset) or bound to a single account.
In: header
Path Parameters
The account's project UUID — from GET /accounts, NOT the Apple asaOrgId. Pass the literal current with an account-scoped key to use its bound account.
Query Parameters
Which level to return.
"all"Value in
- "campaign"
- "ad_group"
- "all"
Restrict to one campaign.
Restrict to one ad group.
Maximum rows to return. Lists rank by spend and truncate; check total and truncated.
1 <= value <= 500200Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/accounts/current/negative-keywords"{ "negatives": [ {} ], "total": 0, "truncated": true}