Preflight schedules Pinterest pins by holding the pin and publishing it through Pinterest's API v5 at the time you chose. It is built for businesses, creators and agencies who post an image to a board and want the same caption, link and alt text to travel with it. Pinterest's API has no field for a future publish time, so the schedule lives in Preflight, and every pin is checked against Pinterest's limits before it is queued.
| Pinterest through Preflight | What the API allows |
|---|---|
| Text limit | 800 characters |
| Media | Pictures only, 5 per post |
| Pictures | Up to 20 MB each |
| Video | Not accepted |
| Thread in one go | No |
| First comment | No |
| Alt text | Yes |
| Edit after publishing | No, the API has no edit |
| Delete from Preflight | Yes |
| Comments | Not available through the API |
| Figures reported | impressions, views, saves, likes, comments |
| Retention and traffic sources | No |
What goes out
One pin per post: a picture, a title of up to 100 characters, a description of up to 800, alt text, a destination link and the board it goes on. The first line of the post becomes the title and the remaining lines become the description. A one-line post is used for both, and a title set in the Pinterest options replaces the first line. Pinterest fetches the picture from a link Preflight gives it, valid for one hour, rather than receiving the bytes.
Only images go out. A video on a Pinterest target is refused at the check, and so is a post with no picture at all. Several pictures on one post are warned about, because only the first is sent. The same pin to three boards is three targets, each with its own board.
Connecting a Pinterest account
You connect with Pinterest's own consent screen. Preflight asks for five permissions: read your account, read boards, read pins, write pins and write boards. The last one looks odd for publishing, but a pin is written to a board and Pinterest refuses the pin without it, so an account connected without it is asked to reconnect.
A business account is not required. Boards are loaded live when you compose, because a pin without a valid board is refused, and the first board is remembered as a fallback. Tokens are renewed automatically, so scheduled pins keep working without you reconnecting.
What fails most often: an account first connected to Pinterest's test environment (Preflight no longer uses it, and the account must be reconnected), a connection granted without board write access, and a token revoked in Pinterest's settings.
What the API allows
| Capability | Allowed | Notes |
|---|---|---|
| Publish an image pin | Yes | Preflight sends JPEG, PNG, WebP, BMP or TIFF, up to 20 MB |
| Publish a video pin | Yes, in the API | Needs a separate media upload; Preflight does not send video to Pinterest |
| Several images in one pin | Yes, in the API | Preflight sends the first picture only |
| Schedule on Pinterest's clock | No | The pin-create call has no publish-at field; Preflight holds the pin |
| Edit after publishing | Yes, in the API | Title, description, link, alt text and board; Preflight does not offer it, so edit on Pinterest |
| Delete | Yes | From Preflight, and a pin already gone counts as done |
| Alt text | Yes | Up to 500 characters |
| Board and section | Required board | Every pin needs a board; you choose it per target |
| Read or reply to comments | No | The v5 reference has no pin comment endpoints |
| Per-pin figures | Yes | Impressions, pin clicks, saves, reactions and comments, up to 90 days back |
What the API refuses
- A pin without a board. The API will not create one. Preflight makes the board a required choice per target.
- A pin from an app with Trial access. Pins and boards made under Trial access are visible only to their creator. Pinterest's apps need Standard access to publish publicly, which takes a recorded demo of the sign-in flow. Preflight's app has it, so pins go to the real Pinterest.
- Scheduling. The app can schedule; the API cannot. Preflight publishes at the time instead.
- Comments. You can read the number of comments on a pin, not the comments. Replies have to be made on Pinterest.
- Other people's pins. The create call is meant for new content you made. Saving someone else's pin is a different call and not something Preflight does.
- A permission added later. A missing scope cannot be fixed by retrying. Preflight stops after the first refusal and marks the account as needing reconnection.
What Preflight checks before a post leaves
- A board is chosen, or the pin is refused.
- A picture is attached, because Pinterest needs one. A video is refused.
- The title is counted against 100 characters, and over that is a warning, since Pinterest shows the first 100.
- The description, which is everything after the first line, is counted against 800. Over that is an error.
- Pictures up to 20 MB. A larger file, or one in a format Pinterest does not read, gets a JPEG copy up to 4,096 pixels on the long side, and the composer says so before anything is sent. Your file is not changed.
- Alt text is cut at 500 characters.
- More than one picture is warned about as not sent.
- A token from the old test environment is refused with an explanation, not a bare error.
The same checks run for a pin sent through the public API or the MCP server. The cross-network numbers are on post limits. Pinterest is included on every plan at pricing.
The platform's rules in short
- Access tiers. Trial access is for exploring, with pins visible only to you. Standard is for real use, and moving up needs a demo video of the sign-in flow and a compliant app. In practice, a scheduler without Standard cannot publish anything your audience will see.
- Rate limits. Pin creation falls under the org_write category: 300 calls a day per app on Trial, 100 a minute per user per app on Standard. In practice, a normal posting schedule is far below it, and a bulk import is where a 429 appears.
- Consent for every action. Pinterest's developer guidelines say an app must not create or edit pins without the user's knowledge, and that each action is chosen by the user. In practice, Preflight publishes only pins a person composed and scheduled.
- Spam. Apps built for spam are prohibited and Pinterest may remove an app at any time. In practice, repetitive mass posting is a risk to the whole integration, not just one account.
- Duplicates. The guidelines do not set a rule on duplicate pins. Spreading one picture over many boards with identical text is still a spam risk, so vary the title and description.
- Login and scraping. Apps may only access an account with authorization, never with a password, and may not scrape. Preflight never sees your Pinterest password.
- Data. API data is to be used for the service the account holder asked for, not sold or combined across accounts. Connected-account figures such as pin analytics are the stated exception.
The walkthrough for scheduling pins is how to schedule Pinterest pins.
Checked against the platform's own documents on 8 October 2026; this is a summary, not legal advice. Sources: access tiers, rate limits, developer guidelines and Pinterest's help page on scheduling pins.
Questions people ask
- Can you schedule Pinterest pins?
- Yes. Pinterest's own tool schedules pins for business accounts, and Preflight does it for any connected account by holding the pin and publishing it at the chosen time, because Pinterest's API has no publish-at field. A board and an image are required.
- How many pins can you schedule?
- Pinterest's help page says a business account can have 10 scheduled pins at once, up to 30 days ahead. Preflight keeps the schedule itself, so that cap does not apply; the limit that does is Pinterest's API rate limit, 100 pin creations a minute per user on Standard access.
- Can Preflight schedule video pins?
- Not today. Pinterest's API accepts video pins, but Preflight sends image pins only, and a video on a Pinterest target is refused before scheduling rather than failing afterwards.
- Why were my test pins invisible on Pinterest?
- Pins created by an app with Trial access are visible only to their creator. Preflight's app has Standard access, so its pins are public; an account connected to the old test environment has to be reconnected.