Pinterest Scheduling API
Schedule Pins for a future time via API.
By André LugPinterest's v5 API has no native Pin-scheduling endpoint. To schedule through PostGate, send the same create-Pin request — board_id, media, title — plus an ISO 8601 scheduled_at; PostGate holds the Pin and delivers it at that instant. Use scheduled_at: "queue" to fill recurring daily slots, and draft: true for approval-first workflows.
Pinterest’s own v5 API has no native Pin-scheduling endpoint — a direct integration has to run its own worker that fires create requests at the right time. PostGate builds that scheduling layer in, so a Pin due next Tuesday is the same request as one you’d send right now, just with one extra field.
How do you schedule a Pin for a fixed time?
scheduled_at and PostGate holds the Pin until that instant, then delivers it the same way an immediate post is delivered.curl -X POST https://postgate.studio/api/posts \
-H "Authorization: Bearer $POSTGATE_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: launch-pin-scheduled-001" \
-d '{
"post": {
"body": "New arrivals just dropped.",
"options": { "pinterest": { "board_id": "1099...", "title": "Launch story" } }
},
"profiles": ["pro_pinterest123"],
"media": ["https://cdn.example.com/launch.jpg"],
"scheduled_at": "2026-09-02T13:00:00Z"
}'How does a recurring queue work?
09:00, 13:30, 18:00) on a profile group, then create Pins with scheduled_at: "queue" instead of a fixed timestamp — each one takes the next open slot. This is the pattern for a Pinterest content calendar you fill ahead of time without hand-picking a publish minute for every Pin.How do draft, scheduled, and immediate differ?
draft: true saves the Pin for a human to approve before it goes anywhere near Pinterest. A fixed scheduled_at locks in a publish time. Omitting both fields delivers immediately. Nothing about the Pinterest payload changes between the three — only when PostGate is allowed to send it.Can you cancel or edit before it fires?
PATCH /api/posts/{id} or canceled with DELETE /api/posts/{id} any time before its scheduled instant. Once delivery starts, board ID and media are locked in — Pinterest has no edit-in-place for a published Pin’s destination board, so a mistake caught late means deleting the Pin and creating a new one.Do scheduled Pins still need an Idempotency-Key?
Idempotency-Key rule applies: PostGate treats a repeated key within 72 hours as the same logical Pin instead of creating a duplicate.Frequently asked questions
Does the Pinterest API support scheduling Pins natively?
No — Pinterest's own v5 API has no native Pin-scheduling endpoint, so a direct integration has to run its own worker that fires create requests at the right time. PostGate builds that scheduling layer in: a Pin due next Tuesday is the same request as one sent right now, just with one extra field.
Can I cancel or edit a scheduled Pin before it publishes?
Yes — a scheduled Pin can be updated with PATCH /api/posts/{id} or canceled with DELETE /api/posts/{id} any time before its scheduled instant. Once delivery starts, board ID and media are locked in; Pinterest has no edit-in-place for a published Pin's destination board, so a mistake caught late means deleting the Pin and creating a new one.
How does a Pinterest posting queue work?
Define a queue with comma-separated daily slots (for example 09:00, 13:30, 18:00) on a profile group, then create Pins with scheduled_at set to "queue" instead of a fixed timestamp — each one takes the next open slot. This is the pattern for a Pinterest content calendar you fill ahead of time without hand-picking a publish minute for every Pin.
Do scheduled Pins need an Idempotency-Key?
Yes. A scheduled request is still a request your own systems might retry — a deploy, a queue redelivery, a flaky connection. PostGate treats a repeated Idempotency-Key within 72 hours as the same logical Pin instead of creating a duplicate.
