Pinterest Ads

Advertiser accounts; campaigns, ad groups and ads; promoted Pins and creative; targeting and audiences; catalogs, feeds and catalog reports; conversion events; and account, campaign, ad-group and ad analytics.

With approved read scopes, retrieve advertising data for campaigns, ad groups and ads; inspect targeting, audiences and catalogs; and obtain performance analytics or generated catalog reports for authorized advertiser accounts.

Under the relevant write scopes, create, update or delete ads, ad groups and campaigns; manage catalogs; create audiences; and send conversion events. Some campaign-structure fields become immutable, including campaign `objective_type`, ad-group `budget_type` and `billable_event`, and ad `creative_type`.

Pinterest API uses OAuth 2.0 bearer tokens with entity-specific read and write scopes such as `ads:read`, `ads:write`, `catalogs:read`, and `catalogs:write`. Authorization Code grants require user approval and provide the full capability range; Client Credentials act for the app owner, require two-factor authentication, and cannot use every sensitive endpoint.

Request the minimum entity scopes needed, distinguish Authorization Code user delegation from Client Credentials app-owner access, expose immutable campaign fields before creation, and keep advertiser-account role checks visible for catalogs and other business-access operations.

No first-party provider MCP was verified. Pinterest API Trial access is limited to 1,000 requests per day; Standard access has a universal 100 requests per second per user per app plus category-specific limits. Access tokens expire after 30 days, continuous refresh tokens must be refreshed within their 60-day window, and catalog reports use build-then-download flows.