Pinterest API integration guide
Create supported Pins for connected Pinterest accounts with explicit board destinations, media, links, and analytics.
Create supported Pins for connected Pinterest accounts with explicit board destinations, media, links, and analytics.
Pinterest integration overview
Create supported Pins for connected Pinterest accounts with explicit board destinations, media, links, and analytics.
A valid board target is essential, and board visibility, account type, link policy, and media format affect publication.
A provider appearing in this guide does not guarantee that every operation is enabled for every account. Use capability discovery before showing a control or promising automation.
Publishing workflows
- Image and supported video Pins
- Explicit destination-board selection
- Pin title, description, and link configuration
Model a post as one parent workflow with a separate target for each Pinterest account. This preserves the resolved content, delivery attempt, provider identifier, error, and retry state for every destination.
Connection and setup checklist
- 1
Configure an approved Pinterest provider app.
- 2
Authorize the business or creator account and sync eligible boards.
- 3
Require board selection and validate Pin/media capabilities before publication.
Media and validation
Validate image or video format, aspect ratio, title, description, link, board, and any alt-text fields before dispatch.
Validate before dispatch as well as during composition because account permissions and provider constraints can change after a draft is saved. Return target-level provider errors with a safe message, stable error code, and request ID.
Feeds, analytics, and engagement
Available Pin feeds and analytics can include impressions, clicks, reactions, and saves without treating missing metrics as zero.
Normalized analytics use null when a metric is unavailable. A missing provider metric is not the same as a measured zero, and client reports should preserve that distinction.
Frequently asked questions
Does App9 Post support every Pinterest feature?
No. Support is determined by the connected account's current capability response, provider permissions, account type, provider review, and App9 Post certification status.
Should my composer hardcode Pinterest limits?
No. Use the capability matrix for live validation and treat documentation as design guidance rather than a substitute for account-level constraints.
Can I use my own Pinterest OAuth app?
App9 Post supports managed and customer-provided provider credentials where the provider connection is available. Customer-owned apps remain subject to the provider's review and policy requirements.