Snap

SnapchatMarketing API

Snapchat Marketing API is a major AR and social-advertising surface open to developers for campaign execution, reporting, attribution, audience management, conversion events, and creator collaboration, with a documented organization, ad-account, ad-squad, creative, and measurement model.

Advertising & media buyingSystem of engagementExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityExtensible SaaS
MCP supportThird-party only
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Organizations, members and roles; funding sources and ad accounts; campaigns, ad squads, ads, creatives and media; audiences, targeting, pixels, catalogs and conversion events; plus entity-level reporting statistics.

02 · Data you can retrieve

Read the organizations and ad accounts available to the OAuth user; retrieve campaign, ad-squad, ad, creative, audience, targeting and catalog state; and query account or entity statistics at TOTAL, DAY, or HOUR granularity.

03 · Actions and write paths

Create and manage campaigns, ad squads, media, creatives and ads; maintain audiences and catalogs; and send conversion data under the broad `snapchat-marketing-api` or separate offline-conversions scope and the OAuth user's assigned roles.

04 · Authentication and permissions

Snap uses OAuth 2.0 bearer tokens. An Organization Admin creates the OAuth app in Business Manager; the `snapchat-marketing-api` scope permits both read and write operations, and each access token reflects the authorizing user's permissions across organizations and ad accounts.

05 · Monitoring, approval, and recovery

Map every token to a maintained organizational user, require both organization and ad-account roles, avoid defaulting an integration user to Organization Admin, and expose which role authorizes each campaign, audience, catalog, or member-management action.

06 · Limits and caveats

No Snap-published MCP provider was verified. Marketing API apps average at most 20 requests per second overall and 10 per second per access token. Access tokens last 60 minutes; stats update about every 15 minutes and finalize 48 hours after day end; large reports use async jobs whose download URLs expire after seven days.

Agent access

MCP support

Third-party onlyCommunity or third-party MCP only

Support: Third-party only

Read scope: No first-party MCP read surface verified.

Write scope: No first-party MCP write surface verified.

Authentication: No first-party MCP auth model is verified. An API-backed adapter uses Snap OAuth 2.0 authorization-code and refresh-token flows; access tokens are bearer tokens valid for 60 minutes and carry the authorizing user's live permissions.

Approval boundary: Because Snap's marketing scope authorizes reads and writes together, a customer adapter must add separate confirmation for funding-source selection, campaign or ad-squad activation, budget and bid changes, creative publication, audience updates, conversion uploads, and destructive member or ad-entity actions.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation2

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Snap ships them.

Single-platform patterns

  • AR creative and campaign operations console
  • Campaign exception cockpit
  • Creative and policy review queue
  • Budget pacing workbench
Use in the brief builder →

Multi-platform compositions

  • Snapchat Marketing API + CRM or revenue system: campaign exception cockpit
  • Snapchat Marketing API + analytics or warehouse + creative-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

7 recorded sources
APIRepresentative source
https://developers.snap.com/marketing-api/home ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Recorded first-party developer source; summary not endpoint-exhaustive

APISource inventory
https://developers.snap.com/marketing-api/Public-Profile-API/GetStarted ↗

Reverified the recorded platform core and MCP boundary: Organizations, ad accounts, campaigns, ad squads, ads, creatives, media, audiences, pixels, catalogs, and reporting statistics.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.

HomepageSource inventory
https://forbusiness.snapchat.com/advertising ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.