Pinterest adds Business Access endpoints for sharing ad accounts and profiles

What this means for you

A business can let other people help run its Pinterest account, like an agency or a new employee. Before, you set that up only on Pinterest's own Business Manager pages. Since April 2024, apps can do it too: send the invite, accept it and decide who may do what. One of those permissions, Publisher, lets someone create and schedule Pins on the business profile.

The details

• Scopes: reads need biz_access:read; invites, permission changes and removals need biz_access:write.
• Endpoints (v5.13.0): under /v5/businesses/{business_id}: invites (GET, POST, DELETE), invites/assets/access and requests/assets/access (POST), members (GET, PATCH, DELETE), members/assets/access (PATCH, DELETE), members/{member_id}/assets, partners (GET, DELETE), partners/assets (PATCH, DELETE), partners/{partner_id}/assets, assets and assets/{asset_id}/members and partners. Plus GET /v5/businesses/employers and PATCH /v5/businesses/invites to accept or decline.
• Roles: Employee, Manager (BIZ_ADMIN in the API) and Partner (internal or external).
• Asset types and permissions: asset types include AD_ACCOUNT and PROFILE. Permissions include ADMIN, ANALYST, FINANCE_MANAGER, AUDIENCE_MANAGER, CAMPAIGN_MANAGER, CATALOGS_MANAGER and PROFILE_PUBLISHER. The spec notes PROFILE_PUBLISHER is only available on PROFILE assets.
• Publisher permission: the guide says it covers creating, editing and deleting Pins and boards, scheduling Pins to publish in the future and viewing individual Pin stats.
• Acting on a shared account: endpoints such as pins/create accept an ad_account_id so the token user can use the permissions they hold on that ad account.
• Asset groups: endpoints for grouping assets (/v5/businesses/{business_id}/asset_groups) arrived later, in the July 2024 changelog and spec v5.14.0.

What to do next

• Business owners: Nothing required. You can still manage access in Business Manager.
• Marketers and agencies: Ask your scheduler whether it supports Business Access, so you can publish to client profiles without sharing logins.
• Developers: Add the biz_access scopes only if you manage access, and use ad_account_id on supported endpoints instead of separate user tokens per client.