Snapchat Ads API

# Fix list: Snapchat Ads API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/snapchat-ads, the October 2026 research run, assessed 8 October 2026. Grade D, 50.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Snapchat Ads API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 34 out of 100, up to 13.2 more on the total

Why it scored 34: Read with the hosted lines, grading the public REST API. No status page is linked from the reviewed documentation, and status.snapchat.com did not connect from our network (0). With no readable incident history, the record scores the brief's 5 (5). Rate limits are published as an average of 20 requests a second per app and 10 per access token (15). 429 is documented with advice to lower the request rate, and the docs say to refresh and retry on a 401 for an expired token. No Retry-After header, backoff schedule or idempotency key was found (4 of 15). No SLA was found (0). The API is v1 and generally available. Reach and Frequency buying is marked beta (10). Total 34.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No x402, MPP or L402 (0). No fee for API access was found and no page states a price for the API. Ad pricing is public, with a $5 daily minimum (10). OAuth app setup has no stated cost and test ad accounts never serve live ads. The quick start lists a funding source among the prerequisites and the help centre article on access could not be read, so no-card access is not established (10). A person has to create the OAuth app in Business Manager and consent in a browser (0). Total 20.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 3. Schema & documentation, 56 out of 100, up to 7.2 more on the total

Why it scored 56: No OpenAPI specification or other machine-readable contract was found (0). llms.txt indexes every Marketing API page and each has a Markdown twin (10). Reference pages describe each entity and endpoint, with a quick start and guides for ad formats, though little on when not to use an endpoint (13 of 20). Attribute tables mark required fields and list allowed values, while targeting travels as nested JSON described by example (11 of 15). Each endpoint has a curl request and a JSON response. The errors page is a table of HTTP codes with placeholder text, and `E` codes are explained only for PATCH, large stats responses and two FAQ cases (9 of 15). One version, v1, with a dated change log back to 2017 and an announcements page. Changes ship in place (13 of 15). Total 56.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 4. Agent ergonomics, 57 out of 100, up to 7 more on the total

Why it scored 57: Stats requests take `fields`, `omit_empty` and `limit`, and no field selection was found on entity reads. The measurement page is about 300 KB of Markdown. The MCP server's tool list is not published (15 of 25). Cursor paging with `limit` from 50 to 1,000, `sort` on four entities, breakdowns and asynchronous reports (18 of 20). Errors carry `error_code`, `debug_message`, `display_message` and a status for each entity in a bulk call, with no full code list, and `E3003` means either no permission or no such entity (13 of 20). No idempotency key was found. Test ad accounts, PAUSED status, eligibility and estimate endpoints and `sub_request_warnings` lower the cost of a wrong write, while PUT resets omitted attributes to defaults (6 of 20). No Ads API SDK was found. Calls need one bearer header and bulk bodies are plain JSON (5 of 15). Total 57.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Security & auth, 65 out of 100, up to 6.1 more on the total

Why it scored 65: OAuth 2.0 authorisation code grant with 60-minute access tokens, a client secret shown once and revocation by the member. The `snapchat-marketing-api` scope covers reads and writes, and refresh tokens do not expire. The MCP server has its own `snapads.read` scope. No documented option puts a token in a URL (22 of 30). Calls follow the member's roles, the reports role is read-only, the MCP server is read-only and needs an admin's approval for each agent, and test ad accounts never serve. No confirmation step for a write or delete was found (14 of 20). The MCP page warns that agents may act on instructions hidden in tool outputs and gives no mitigation. Lead form responses and creator content are third-party text (7 of 15). Change logs return user, app and before and after values for five entity types (12 of 15). security.txt points to a HackerOne programme and the DPA promises breach notice within 72 hours. No SOC 2 or ISO 27001 statement was found in the pages read (10 of 20). Total 65.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 6. Maintenance & community, 61 out of 100, up to 3.4 more on the total

Why it scored 61: The change log's latest entries are dated 6 October 2026, two days before the check (30). It has 18 dated entries between 10 July and 6 October 2026 (20). Closed service with a dated change log, an announcements page and a newsletter. Support runs through the business help centre, which our reader could not read (8 of 15). No SDK for the Ads API. The only official client is the Java SDK for the Conversions API (3 of 15). No public repository or CI was found (0). Total 61.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 69 out of 100, up to 2.7 more on the total

Made of editorial 57, provenance 80.

Why it scored 69: Editorial half only. Closed service with clear terms. The Snap Developer Terms are effective 31 January 2025 and incorporate the Business Services Terms (15 of 30). The privacy policy is effective 21 September 2026. The DPA sets breach notice within 72 hours where feasible, return or deletion at termination and 30 days' notice of a new sub-processor, and the developer terms limit what a developer may retain. No retention periods for advertiser or reporting data were found (20 of 30). Deprecations are dated in the change log and announcements, such as the 35+ age bucket on 15 October 2026, and a 2020 notice gave 90 days. The Business Services Terms reserve the right to modify or discontinue any service without notice (14 of 20). The DPA links a sub-processor list with purposes and locations on the help centre, which our reader could not read (8 of 20). Total 57.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: read, states 3 of the 7 things a reader expects, and has 2 clauses that cost points (2.6 of 10)
- Privacy policy: read, states 7 of the 8 things a reader expects, and has 1 clause that costs points (7.3 of 10)
- Status page: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: businesshelp.snapchat.com articles (script-drawn), so the API access guide, the roles article and the sub-processor list were not read
- unchecked: status.snapchat.com did not connect from our network, so whether Snap runs a public status page for the Ads API is not established. None is linked from the docs read
- unchecked: the HackerOne programme page (JavaScript only), so bounty scope and rewards were not read
- unchecked: the Ads MCP server's tool list and annotations, which are not published in the docs. We did not connect to it
- Whether a business account needs a payment method before an OAuth app or a test ad account can be created
- Whether Snap holds SOC 2 or ISO 27001 certification for its business services. No statement was found in the pages read
- Whether an OpenAPI specification or an Ads API SDK exists outside the pages reviewed. None was found
- The lead described the interface as a REST API with OAuth, which is right. It did not mention the Ads MCP server launched in August 2026
- security.txt has no Expires field and is recorded as valid, as on comparable listings

## Weaknesses

- No OpenAPI specification, Postman collection or Ads API SDK was found in the reviewed documentation
- No status page or SLA was found, and no Retry-After header, backoff schedule or idempotency key is documented
- The `snapchat-marketing-api` scope covers reads and writes together, and refresh tokens do not expire
- An update with PUT expects the whole object and resets omitted attributes to their defaults. Deleted objects cannot be restored
- The Snap Developer Terms forbid public statements about use of the developer programme without Snap's written approval, and the Business Services Terms forbid publishing Business Services Data

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Refresh the access token every 60 minutes with the refresh token. An expired token returns 401 with `WWW-Authenticate: Bearer error="invalid_token"`
- Create a test ad account with `"test": true` and build there first, and create campaigns with `"status": "PAUSED"`
- Change one field with PATCH (JSON Patch). A PUT that omits attributes resets them to their defaults
- Send money as micro-currency, where 1.00 of the account currency is 1,000,000
- Page lists with `limit` (50 to 1,000) and follow `paging.next_link`. Use `async=true` for large stats pulls, since an oversized response fails with `E9001` and a retry does not help

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.