# Get API access to an advertiser's account

> Get API access to an advertiser's account: 2 companies fully do it, 7 with a limit, 10 carry the tag. Every listing in Advertising & campaign operations with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/advertising.get-access/
- Markdown: https://www.anchorterminal.com/niches/advertising.get-access/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/advertising.get-access/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/advertising.get-access/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 7 | 10 | 28 | 8 |

## What counts as done

The agent makes its first successful production read on the account, with the time from application to that call recorded; for a read-only job, no approval tier beyond read is needed.

How agents ask for it: connect our Google Ads account; why can't the agent see our Amazon campaigns; set up the X Ads MCP

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Apple Ads Platform API (Apple Inc.)**: An account administrator grants an API role, the client credentials token is requested directly, and GET /v1/acls lists every ad account and role the caller holds; acc-22 found no approval gates on the credential path.
- **Microsoft Advertising API (Microsoft Corporation)**: Any Microsoft Advertising user can press Request Token for a universal developer token, with no access tier or review described, and the sandbox takes the shared token BBD37VB98, so a read can start the same day.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Amazon Ads API (Amazon.com Services LLC)**: Access needs an approved developer application plus the advertiser's consent, and acc-09 was still pending after 29 days and four submissions while acc-10 ran 8 business days past the promised reply with no answer.
- **Google Ads API (Google LLC)**: Explorer access is reviewed automatically in most cases and allows 2,880 production operations a day, enough for reads, but acc-06 was rejected within seconds with no email, and Basic needs a design document (acc-07).
- **LinkedIn Marketing APIs (LinkedIn Corporation)**: Development tier gives read-only reporting on unlimited ad accounts with r_ads_reporting, but the app must first be approved for the Advertising API product, LinkedIn reviews at its discretion, and no review time is stated on the page.
- **Meta Marketing API (Meta Platforms, Inc.)**: Adding the Marketing API product gives Limited access by default and the official MCP server needs only ads_read for reporting, but acc-04 hit a video-selfie identity check and Community Review on the person's own account.
- **Refersion MCP (Refersion Inc. (New Jersey corporation, a subsidiary of EH ZO 1 Holdings LLC per its terms))**: The MCP consent screen splits permissions by area and by read or write, so a read-only grant is possible with no developer review, and unverified clients are allowed but flagged, but which paid plan includes the MCP server isn't stated.
- **Snapchat Ads API (Snap Inc.)**: Supported agents use Snap-registered client IDs on the read-only MCP server, approved by an Admin at sign-in, so no developer application is needed for reads, but a client id from your own OAuth app fails with invalid_client, so only named agents connect.
- **X Ads API (X Corp.)**: Access is by the Ads API Access Form, reviewed within 3 business days, and the MCP server's ads.read scope alone gives a read-only agent, but X keeps one live OAuth grant per app and user, and acc-19 found Codex's OAuth failing origin validation.

- not this job: FetchIQ (LeadingResponse): There is no programmatic access to apply for; accounts are for LeadingResponse clients, signed in through a browser.

## What stops agents finishing

- developer application pending for weeks with no reply (Amazon)
- access tier needing a design document or manual audit (Google Basic, Standard)
- identity check on the person's own account (Meta)
- official MCP OAuth refusing the agent's client

## Around it

After: advertising.performance-report.

## Where this comes from

Weight 28 of 100 in Advertising & campaign operations: 8 of 28 counted mentions (acc-04, 06, 07, 09, 10, 19, 22, 25); Amazon's docs repository had eight onboarding-blocker issues filed between 8 October and 14 November 2026

As data: https://www.anchorterminal.com/api/v1/use-cases/advertising.get-access.json, or the MCP tool get_use_case with id advertising.get-access. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
