Included as Reddit's programmatic community-advertising surface: the open v3 API covers campaign operations, community and interest targeting, posts and creative assets, audiences, product catalogs, leads, conversion signals, feature access, and performance reporting.
Concrete capability record
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.
Businesses, profiles, ad accounts and account history, funding instruments, campaigns, ad groups, ads, posts and structured posts, creative assets, custom and saved audiences, targeting taxonomies, lead-generation forms, product catalogs and feeds, pixels and conversion signals, measurement resources, reports, and feature-access records.
List authorized businesses, profiles, ad accounts, campaigns, ad groups, ads, posts, creative assets, audiences, targeting values, catalogs, leads, pixels, and conversion or measurement state; query feature access; generate paginated performance reports with selected metrics, filters, and breakdowns.
Create or update supported campaigns, ad groups, ads, saved or custom audiences, posts and structured posts, lead forms, product catalogs and feeds, and conversion or measurement events when the token scope, user permission, and account feature access allow it.
All applications use OAuth 2.0 access and refresh tokens. Request only the needed accepted scopes: adsread, adsedit, adsconversions, adsleadgendownloader, adsmeasurement:read, and adsmeasurement:write. A 403 can also reflect the authenticated user's account permission or missing feature access, not only a missing scope.
Record the authorizing Reddit user, business, ad account, OAuth scopes, and feature-access response. Gate budget, status, audience-ingestion, lead, catalog, and measurement actions separately, and monitor the endpoint group's returned rate-limit policy and remaining quota.
The v3 Ads API is open to developers without account allowlisting, but alpha and beta products are unsupported unless explicitly stated and individual features may still require account access. Campaign-management reads are limited to 400 requests per 60 seconds, writes to 200, and reports to 60; Conversions API uses separate limits without the standard headers. List operations are paginated. Report metrics can take up to six hours to stabilize, delivery history is 24 months, and reach/frequency history begins in June 2024.
First-party access
Agent access
Support: Third-party only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Reddit's v3 documentation defines OAuth for Ads API clients; this packet does not convert that contract into an official MCP auth claim. A customer-built adapter would use access and refresh tokens with only the scopes needed for read, edit, lead download, conversions, or measurement.
Approval boundary: Confirm business and ad-account context before budget, campaign-state, targeting, audience, ad, structured-post, catalog, lead-form, conversion, or measurement writes. Recheck feature access immediately before offering gated controls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
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 Reddit ships them.
Evidence and dates
“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.
Businesses, ad accounts, campaigns, ad groups, ads, creative assets, posts, custom and saved audiences, catalogs, pixels, conversion events, and reports. Create and update campaigns, ad groups, ads, audiences, posts,…
Targeted first-party core-access review
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
