Image Pins
An image URL becomes a Pin with your title and description.
Pinterest · Discovery
The Pinterest API, a Pin in one call
Create Pins on a board with Pinterest API v5. We take your image URL, title, and description and post the Pin — you pick the board once.
PinsBoardsRich linksScheduling
Official OAuth APIup to 500 charsPinterest API v5
publish-pinterest.ts
curl https://postmyish.com/api/v1/posts \
-H "Authorization: Bearer $POSTMYISH_KEY" \
-H "Content-Type: application/json" \
-d '{"caption":"12 desk setup ideas for 2026","platforms":["pinterest"]}'201 · { id: "9f2c8b1e…", status: "published" }JSON
Why not raw?
Pinterest API v5 is powerful — and painful
The official API can do this. It just makes you do a lot first. Here's what raw Pinterest publishing costs you, and what PostMyIsh absorbs.
Raw Pinterest API
With PostMyIsh
Media
media_source with a source_type and hosted image URL
Pass a URL; we build the media_source
Auth
OAuth, and the app reviews out of trial mode
One OAuth screen, one encrypted token
Board
Every Pin needs a board_id you look up
We store your board id on connect
Trial limits
Trial apps are capped until Pinterest reviews them
We surface the cap; nothing fails silently
Capabilities
Everything Pinterest supports, one endpoint
Post types, limits, and scheduling — all through the same POST /v1/posts call, formatted the way Pinterest expects.
Board targeting
Pick the board once at connect time; every Pin lands there.
Rich descriptions
Up to 500 characters of description under the Pin.
Scheduling
Queue Pins with schedule_at for a steady cadence.
Copy, paste, ship
Real calls, not pseudocode
Every snippet hits the live API — same base URL, Bearer auth, plain JSON. Add your key and it runs.
Publish to Pinterest now
One POST fans out to Pinterest. The response carries the id and status the moment it ships.
publish.txt
curl https://postmyish.com/api/v1/posts \
-H "Authorization: Bearer $POSTMYISH_KEY" \
-H "Content-Type: application/json" \
-d '{"caption":"12 desk setup ideas for 2026","platforms":["pinterest"]}'How it works
Live in three steps, not three weeks
Connect Pinterest, call one endpoint, and we run the Pinterest API v5 plumbing behind it.
Step 01
Connect the account
Link it once from the Accounts page through its official login. The credential is stored encrypted.
Step 02
POST /v1/posts
Send one caption and the platform id. Add schedule_at to queue it, or media for a URL.
Step 03
We handle the rest
Container flows, token refresh, rate limits, and the real post id — all on our side.
Straight talk: Pinterest apps start in trial mode with caps until reviewed. With a token and board id stored, the Pin-creation call is complete and posts for real.
One API, eleven more
Pinterest is one entry in the same array
Add another id to platforms and the identical call posts there too. One request already covers Pinterest, Instagram, and Facebook — no second integration.
Pinterest API FAQ
The honest answers
What's real, what needs review, and what Pinterest itself requires — no hand-waving.
Is this the official Pinterest API?
Yes — Pinterest API v5, the POST /v5/pins endpoint.
Do I need an image?
Yes — a Pin is fundamentally an image. Pass a public image URL as media and it becomes the Pin.
Which board does it post to?
The board id you set when connecting. You can reconnect to change it.
Is there a review?
Pinterest reviews apps to leave trial mode. The Pin-creation code works in trial for your own account; review lifts the caps.
Ready to post your ish everywhere?
Connect your accounts, write one caption, and be live on every feed in minutes. The free plan is genuinely free.