API
One POST, and it is published
Send account_id, board_id and image_url. Pincast answers 201 with a pin id you can follow.
Submit a pin and Pincast handles the queue, the pacing, the retries and the webhooks. You never write Pinterest plumbing again.
Read the docsDurable queue
A submitted pin is a published pin: the queue survives incidents and redeploys.
Automatic pacing
Pincast spaces publications out to stay under the Pinterest API limits.
Retries
A transient failure is retried with a growing backoff, with nothing to do on your side.
OAuth, token encryption, queueing, pacing, retries, webhooks: it is all in place. You only write the call you care about.
Foundations
Wired
Your users authorise Pincast on their Pinterest account; tokens are encrypted and refreshed.
Immediate or scheduled pins, pacing respected per account, retries with a growing backoff.
Every pin carries a status, an attempt count and, on failure, an error code you can act on.
Publication, failure, disconnection: your endpoints are notified and the HMAC signature is verifiable.
Your agents publish to Pinterest with the same guarantees as the API, with no extra code.
Several Pinterest accounts per organization, several members, each with a role.
Without Pincast
You write the OAuth exchange, the token storage, the queue, the retries and the monitoring - before publishing a single pin.
With Pincast
You connect a Pinterest account once, then call Pincastfrom your code, your CMS or your automation.
What you would otherwise spend weeks wiring by hand, already shipped in Pincast.
API
Send account_id, board_id and image_url. Pincast answers 201 with a pin id you can follow.
Queue
Every pin is stored before it reaches Pinterest. A network incident or a redeploy makes no publication disappear.
Pacing
Pincast spaces out publications on the same account to stay under the v5 API limits, and honours Retry-After headers.
Webhooks
pin.published, pin.failed and account.disconnected reach your endpoints, signed with HMAC-SHA256.
OAuth
Pinterest tokens are encrypted with AES-256-GCM and renewed before they expire. A revoked token fires a webhook.
MCP
The same operations are exposed over REST, an MCP server and a CLI - one definition, three surfaces.
Start free and upgrade when you need more. No hidden fees.
Try the API and publish your first pins
$0
USD / monthFor a site or shop publishing every day
$19
USD / monthFor agencies and high-volume integrations
$49
USD / monthPincast is a Pinterest publishing API. You connect a Pinterest account through OAuth, then submit pins over HTTP: the queue, the pacing, the retries and the webhooks are handled for you.
For the API, yes - a single HTTP call, from your own code, an n8n node or a script. The dashboard also lets you publish and schedule a pin without writing a line.
That is the pacing: Pincast spaces out publications on the same account to stay under the Pinterest API limits. The pin will go out on its own - do not resubmit it.
Encrypted with AES-256-GCM, never in clear text. They are renewed before they expire, and you can disconnect an account at any time from the dashboard.
Every request carries an X-Pincast-Signature header. Compute the HMAC-SHA256 of timestamp.body with your endpoint secret and compare it to the v1 value.
The API answers 402 with the quota_exceeded code. The quota counts pins actually published: a failed or cancelled pin consumes nothing.
Connect a Pinterest account, create an API key, send your first request. Pincast takes care of the rest.
Start for free