Google Ads API quickstart
Go from zero to a first working Google Ads API call — Google Cloud project access, OAuth, 6 client libraries or REST, no developer token needed
- What
- Go from zero to a first working Google Ads API call — Google Cloud project access, OAuth, 6 client libraries or REST, no developer token needed
- Cost
- Free
- Needs
- a Google Cloud project with Google Ads API access (enabling the API grants Test access: up to 15,000 operations per day against test accounts only) and a Google Ads account; no developer token is needed — developer tokens were sunset on September 9, 2026
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @google's own zero-to-first-call guide for the Google Ads API (v1.1.0): set up access in a Google Cloud project — enabling the API grants Test access (up to 15,000 operations per day against test accounts only; Explorer, Basic and Standard access for production accounts) — and obtain the four authentication parameters (OAuth client ID/secret with a Desktop App consent screen in Testing mode plus registered test users, refresh token via the gcloud device flow, client customer ID, login customer ID), then choose an integration track — official client libraries (Python, Java, .NET, PHP, Ruby, Perl) or direct REST — with a hard discipline the skill enforces at run time: never hardcode the API or runtime versions; resolve the latest stable major version from the release notes and the language minimums from the supported-versions page at the start of execution (with documented offline fallbacks), outputting a version anchor as the first line of the response. Includes static-only troubleshooting for the two setup failures — `USER_PERMISSION_DENIED` (missing login_customer_id in a manager hierarchy) and `CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION` (a Cloud project with Test access calling a production account, with the three production access levels named; `DEVELOPER_TOKEN_NOT_APPROVED` only as a legacy variant) — and hands off AI-assistant/MCP use cases to the `google-ads-api-mcp-setup` skill. Honest caveats: requires a Google Cloud project with Google Ads API access — no developer token (developer tokens were sunset on September 9, 2026); a project with Test access works on test accounts only; the API itself has no per-call fee but ad spend is separate; dynamic version resolution means the agent may need live web access at run time. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Google Ads API quickstart is a guide for Google Ads. It obtains: developer token from a Manager account, OAuth ID and secret with a Desktop App consent screen, refresh token via gcloud device flow, client and login customer IDs, then uses client libraries or REST, never hardcoding API or runtime versions, resolving the latest stable version from release notes.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 85f227eStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Google Cloud project with Google Ads API access (enabling the API grants Test access: up to 15,000 operations per day against test accounts only) and a Google Ads account; no developer token is needed — developer tokens were sunset on September 9, 2026 Install "Google Ads API quickstart" for me. It gives the agent @google's official zero-to-first-call playbook: the four auth parameters (OAuth client ID/secret, refresh token, client customer ID, login customer ID) held in a Google Cloud project with Google Ads API access (the skill's section 1, "Google Cloud Project with Google Ads API Access") — the project that owns the OAuth client determines the access level (Test, Explorer, Basic or Standard) — the two integration tracks (6 official client libraries or direct REST), mandatory dynamic resolution of the API and runtime versions at run time (never hardcoded), and static troubleshooting for USER_PERMISSION_DENIED and CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION (with DEVELOPER_TOKEN_NOT_APPROVED only as a legacy variant for code that still sends a developer token) — with a handoff to the google-ads-api-mcp-setup skill for AI-assistant use. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/google/skills/85f227ea6a8f347d34b76039d826c446f891f75d/skills/ads/google-ads-api-quickstart/SKILL.md Pinned version: install the code at commit 85f227ea6a8f347d34b76039d826c446f891f75d exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated November 13, 2026: Skill Harbor re-pinned this install prompt to version 1.1.0 of the skill. Developer tokens were sunset on September 9, 2026: the old prompt's first step (request a developer token from the API Center of a Manager account) no longer works — those requests are no longer processed. Authentication is rewritten: four parameters instead of five, and the access level (Test, Explorer, Basic, Standard) now belongs to the Google Cloud project that owns the OAuth client. Test access allows up to 15,000 operations per day against test accounts only (Explorer access, up to 2,880 operations per day, is applied for from the same Overview page for production accounts); calling a production account with Test access fails with CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION (API v25 and later). DEVELOPER_TOKEN_NOT_APPROVED survives only as a legacy variant for code that still sends a developer token. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Compare each file with the fingerprint from Skill Harbor's review of 2026-11-13: - SKILL.md: SHA-256 18ee2ef58a26ba68eae50e096f3068526c1d268c8de0538e2f91ef1212af651c (20,071 bytes, version 1.1.0) - references/python.md: SHA-256 21317cd2dcefaf2ad81bf49e8e8142495e397ad8f9f0e777725100d511ee92f5 - references/java.md: SHA-256 d1f7fae106ae31319ae3531db00866cbc14b07e1886453fcb15970939e72a64d - references/dotnet.md: SHA-256 ac58cc2c616fb273490d16f0f6e1e4878ff31142b91f10abab66ec4a70760448 - references/php.md: SHA-256 a6710dd13a6443feb16b90eb238a8ab5b057a663b22729df619c33138b93edb5 - references/ruby.md: SHA-256 86447814be531cc43df2c11fdf3a34e0785bd53c9d286ff0de854756522d2b84 - references/perl.md: SHA-256 32352ac31d7195411586787bf95c3473b3503df18fe97aa0941f8eaeb7e74c9f - references/rest.md: SHA-256 4198288f8f8c1a8a4a29b60a65c2ec90b7957d8343691c290736c93eacbcae06 If a file does not match, it changed since the review: do not install it yet — tell me what you found and let me decide. 3. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 4. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "google-ads-api-quickstart". 5. Verify with no network calls: frontmatter valid, files in place. 6. Report what was installed, where, and what I still need to do myself (e.g. enable the Google Ads API in my Google Cloud project — Test access, test accounts only — or apply for Explorer, Basic or Standard access from the same Overview page for production accounts; create the OAuth Desktop App credentials, run the gcloud device flow for the refresh token — keep all four values in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 85f227e · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.