01 · Records and state owned
Organizations, ad accounts, campaigns, ad squads, ads, creatives, media, audiences, pixels, catalogs, and reporting statistics.
Snap
Snapchat Marketing API
Curated major addition platform in ar and social advertising with material relevance to the Marcom operating stack and a first-party developer surface.
Advertising & media buyingSystem of engagementExtensible SaaS
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.
02 · Data you can retrieve
Retrieve authorized campaign hierarchy, creative and audience objects, delivery status, conversion configuration, and performance statistics.
03 · Actions and write paths
Create and update supported campaigns, ad squads, ads, creatives, audiences, media, and measurement objects.
04 · Authentication and permissions
Snap OAuth 2.0, business/ad-account membership, application approval, and endpoint scopes apply.
05 · Monitoring, approval, and recovery
Preserve spend approvals, creative review, audience privacy, account hierarchy, and network-specific advertising policy.
06 · Gaps and implementation limits
Only third-party/community MCP was verified. Marketing API access, features, quotas, and approval may vary by account and partner status.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
Third-party/community MCP only; no first-party provider verifiedCommunity or third-party MCP onlyNo first-party provider verified
Role: third_party_only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
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 interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Snap ships these experiences.
Single-platform patterns
- AR creative and campaign operations console
- Campaign exception cockpit
- Creative and policy review queue
- Budget pacing workbench
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
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.
2 recorded sources
APIRepresentative source
https://developers.snap.com/api/marketing-api/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Recorded first-party developer source; summary not endpoint-exhaustive
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 the representative first-party source or targeted access review.
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.