Create Pins
from your own product.
A Pin is an image, a description, and usually a link back to you. MonoChalk lets your product create and schedule Pins on a user's board through the same unified post request you use for every other network — no separate Pinterest integration to maintain.
What goes into a Pinterest post.
- Image · required
- Every Pin is visual. Upload an image or pass a URL; MonoChalk ingests and validates it before publishing.
- Title & description
- Your unified
textmaps to the Pin's title and description — the same field you set for every platform. - Destination link
- Include a link so the Pin drives traffic back to your page. Optional, but it's what makes Pinterest a distribution channel.
- Board
- The Pin is created on the connected account's board. Your users authorize their own account and boards via managed OAuth.
- Timing
- Add
scheduled_atto publish later, or omit it to publish now. Cancelable before processing.
An image, a caption, a link. Published.
Reference an uploaded image, set your text, and target the connected Pinterest account. MonoChalk validates the Pin and returns a per-target status you can track.
Request API access// image required for every Pin
{
"account_ids": ["pin_3390"],
"text": "10 dashboard layouts we love",
"media": [{ "media_id": "med_ff21" }],
"link": "https://yoursite.com/blog/dashboards"
}
1 Pin queued
Pinterest publishing FAQ.
What do I need to create a Pin through the API?
A Pin needs an image, so every Pinterest post includes media. Your post text becomes the Pin's title and description, and you can include a destination link. MonoChalk validates these before publishing to the connected board.
Can I schedule Pins?
Yes. Send a scheduled_at timestamp to publish a Pin later, or omit it to publish immediately. Delivery is tracked per target with retries on safe failures and signed webhooks.
Do my users connect their own Pinterest accounts?
Yes. MonoChalk manages the OAuth flow and encrypted tokens, so each of your users connects their own Pinterest account and boards through one consistent account model. See the unified API →