Scheduling to Pinterest through SkedCast's API#
SkedCast's /v1 REST API schedules image and video Pins to Pinterest the same way it does every other platform: one POST https://api.skedcast.com/v1/posts call with a content caption and a targets block naming the connected accounts. You need a Pinterest business account, connected once through the console (or minted as a self-serve connect link via POST /v1/clients/:id/connect-invites).
SkedCast is not a raw wrapper over Pinterest's own developer API — it is one versioned, platform-agnostic contract that fans a single compose call out across every connected network, with the Pinterest-specific fields listed below folded into the same request shape.
Pinterest-specific fields (`variants[].overrides.pinterest`)#
| Field | Notes |
|---|---|
boardId | **Required.** A Pin's board is a real destination choice our API cannot guess — the content gate returns a 422 naming the field if it's missing. |
Example: schedule a post to Pinterest#
{
"clientId": "…",
"content": "5 layout ideas for a small studio apartment.",
"targets": { "mode": "accounts", "accountIds": ["…"] },
"schedule": { "type": "at", "at": "2026-10-01T09:00:00" },
"variants": [
{ "platform": "pinterest", "overrides": { "pinterest": { "boardId": "654321098765432109" } } }
]
}Pinterest facts#
| Fact | Value |
|---|---|
| Max caption length | 800 characters |
| Media per post | 5 image or video per Pin. |
| Native platform scheduling | No — SkedCast's managed engine holds the timer |
| SkedCast's default pacing | 20 posts/day, ~30 min apart per account (conservative anti-ban default — not Pinterest's own published rate limit; see the rate-limit guide below) |
Published-post URL (permalink) | https://www.pinterest.com/pin/{id}/ — always derivable from the stored external id. |
Reading status and results#
GET https://api.skedcast.com/v1/post-targets/:id returns the Pinterest target's status (scheduled, published, failed, …), plus error, statusReason, and retryAt when it's parked waiting on something — SkedCast's own pacing, a platform rate limit, or media still transcoding, each with its own machine-readable reason. Once published, externalId and permalink (see the table above) point at the live post.
- Subscribe to
target.published/target.failedwebhooks (or the legacypost.*pair) instead of polling — see [Webhooks](/developers/webhooks). - Or connect an MCP client and ask an agent to check — see [Connect an AI agent](/mcp).
FAQ
- What can I schedule to Pinterest through the API?
- Pinterest posts of type: image and video Pins, via one `POST https://api.skedcast.com/v1/posts` call — the same endpoint used for every other connected platform.
- How do I authenticate against the Pinterest API endpoint?
- The same way as every `/v1` route: an API key (`Authorization: Bearer sked_live_…`) or an OAuth 2.1 bearer token, scoped to `posts.compose` to schedule and `posts.read` to read back status. See Authentication.