Burnpedia Pin Scheduler for Pinterest

This plugin is Pinterest automation for WordPress: it makes Pinterest Pins from the content you already publish. It connects your site to your Burnpedia account: when a post goes live, it builds a draft Pin from the post’s image, title and link; you approve it with one tick, and Burnpedia publishes it to the board you picked, on a schedule, without you opening Pinterest.

How Burnpedia Pin Scheduler for Pinterest is different

It is built for Pinterest alone:

• Up to six Pins from one post, each from a different picture in it, a day apart.
• Your older posts too, spread over the days ahead, not in one burst.
• A free Pinterest check-up of your posts (up to 5,000 a scan), each one listed with a link to fix it.
• A plain reason for every post it skips, in the Activity log.
• Every Pin is one you chose, and its screen says why.

What it does

• Drafts a Pin when a post is published, for you to approve in Burnpedia — or only for the posts you tick.
• Pins posts, pages, WooCommerce products and any other public post type you switch on.
• Uses the featured image, else the post’s first image, else a free cover designed from its title.
• Makes up to six Pins from one post, each using a different photograph, a day apart.
• Sends each Pin to one board, a board per category or one named after your site, and creates a board that is missing.
• Writes the Pin title and description from templates with {title}, {excerpt}, {site} and {categories} tags — editable per post.
• Adds UTM tags to the link (utm_source=pinterest…) so Pinterest traffic shows in Google Analytics.
• Schedules with a delay so caches are warm, retries by itself, and waits out a used-up daily allowance.
• Bulk-pins the posts you published before installing, spread over safe best-time slots.
• Runs a free Pinterest check-up — a Pinterest SEO check — of every published post, up to 5,000: no big, tall image, a title Pinterest would cut, a description too short to be found, no alt text, never pinned — each with a link to fix it.
• Uses a tall picture further down a post when the featured one is wide — one click, one post or all, free.
• Shows how many of your posts are ready for Pinterest, and re-checks them by itself every week — inside WordPress, nothing sent.
• With AI credit (optional), writes Pin titles and descriptions and makes cover images, for one post or many: price shown first, a preview before anything is pinned, each one undoable.
• Writes alt text with AI for every picture a post’s Pins use — one post or many. Optional.
• Reports impressions, saves and link clicks for this site’s Pins — the site total on every plan, per post on the paid plans.
• Shows what happened, per post, in an Activity log — including the posts it skipped and why.

Works on the free plan

Nothing here is locked by the plugin: no trial, no time limit, no feature switched off until you pay us for the plugin. A free Burnpedia account publishes up to 3 Pins a day, and the whole publishing side works on it.

Paid plans add the per-post breakdown and a higher daily allowance. AI words, covers and alt text use AI credit: paid plans include some every day, and anyone can buy a one-time bundle, no plan needed. See burnpedia.app/pricing.

External services

This plugin is a client for Burnpedia, a Pinterest scheduling service at https://burnpedia.app. The plugin cannot work without it: Burnpedia holds the Pinterest connection.

Nothing is sent until you take one of the steps below. With no key saved, a request leaves only after you press a button for it — the one-press connection below, or a bug report — open More plugins, or switch on the install count. Nothing happens on activation.

Connecting this site in one press (optional). On the Connection screen you can press Connect this site to Burnpedia. When you press it:

• Your browser opens https://burnpedia.app/connect/wordpress, carrying the address of this site and its title, so the approval screen can name the site, and which plugin and version asked. It also carries a random one-time request ID and a fingerprint of a secret your browser never sees.
• While you approve it there, this site asks POST https://burnpedia.app/api/site-connect/claim at least three seconds apart, at most 100 times each time the Connection screen is opened while the request is live, and once each time you press I have approved it. Each ask sends that request ID and the secret, and names the plugin and its version in its headers; it does not carry your site’s address, not even in its User-Agent header. Once you approve, the answer is an API key, saved for you and never shown in your browser.
• The request expires after fifteen minutes and its key can be collected only once. If you press Cancel, or the request expires, the asking stops and no key is created.

Once a key is saved, the plugin contacts https://burnpedia.app/api/v1 in these situations:

1. When you open the plugin’s settings screen or press “Check connection” — a GET /api/v1/me request that returns your Burnpedia plan, the Pinterest accounts connected to it, how much of today’s Pin allowance you have used and when it resets, and, during a Pro trial, the days left and a short-lived checkout link. Sent: your API key. Other screens reuse it for five minutes.
2. When you press “Load my boards” — a GET /api/v1/boards request. Sent: your API key and the Pinterest account you picked (account), if any.
3. Whenever a Pin is sent (a post published with “Draft a Pin when a post is published” on, “Pin this post now”, “Send a test Pin”, “Run it now”, Pin older posts, held-back posts, retries) — a POST /api/v1/pins request. Sent: your API key, the Pin title, the Pin description, the post’s public permalink, the URL of the post’s image and that image’s alt text from your Media Library (if any), the board name or id, the Pinterest account you picked (account, if any), and the time the Pin should be published. When a person chose the Pin (“Pin this post now”, “Send a test Pin”, a ticked post, a kept cover), it also sends picked: true; without it, Burnpedia keeps the Pin as a draft for your OK. With no image and “design a cover from its title” on, no image URL is sent; a flag asks Burnpedia to design the cover from the title. With “let Burnpedia generate one with AI” also on, the same flag asks for a generated photograph behind it, which spends AI points on your Burnpedia account; if it cannot be generated you get the free designed cover instead. Nothing extra about your site is transmitted for either.
4. When you open the “Pins from this site” tab — GET /api/v1/pins requests (the list and its counts). Sent: your API key and this site’s address, so that Burnpedia returns only this site’s Pins.
5. When you open the “Pins from this site” tab, or the posts list in WordPress — a GET /api/v1/analytics/site request. Sent: your API key and this site’s address. It returns the impressions, saves and clicks Burnpedia has already recorded for your Pins; it does not ask Pinterest anything.

6. When you press “Make a preview” under “Try an AI cover” in the post editor — a POST /api/v1/covers request. Sent: your API key, the Pin title, the post’s public permalink, and a flag asking for an AI photograph. It uses AI points (cost and balance shown first) and creates no Pin; the preview is shown straight from burnpedia.app, and the picture is pinned only if you press “Pin with this cover” (item 3).

7. When you press “Scan all posts” on the Pinterest check-up tab — POST /api/v1/pinned-status requests, up to 500 addresses each. Sent: your API key and the public addresses (permalinks) of your published posts that this plugin has not pinned yet. It returns, for each address, whether it was ever pinned by your Burnpedia account or is on your connected Pinterest account. Every other check-up result — picture size, alt text, title length, description — is worked out inside WordPress and is not sent anywhere. With no key saved, nothing is sent.

8. When you press “Make it with AI” on a post in the Pinterest check-up — a POST /api/v1/copy request, then the POST /api/v1/covers request described in item 6. Sent to /copy: your API key, the post’s title, its public permalink, and its excerpt (or its opening words). It returns a Pin title and description for that post and uses AI points (price shown first); nothing is pinned until you press “Pin with this cover”. “Write titles & descriptions” sends the same /copy request once per ticked post, without the cover; posts that already have their own words are skipped and nothing is sent for them. “Make cover previews for the ticked posts” sends both requests per ticked post; kept covers go out through item 3, one a day.
9. When you press “Write alt text with AI” (or “Write alt text for the ticked pictures”) in the check-up — a POST /api/v1/alt-text request per picture. Sent: your API key, the public address of a picture that post’s Pins use, and the post’s title. Burnpedia fetches the picture to describe it and returns one sentence, saved as the picture’s alt text. It uses AI points. Nothing is sent for a picture that already has alt text.

An AI request Burnpedia cannot complete is not charged.

The tall-picture choice, the readiness score, the “scan again” reminder and the weekly re-check of your posts all run inside WordPress and send nothing.

The Buy AI credit buttons are ordinary links to https://burnpedia.app/buy-credit, carrying the chosen bundle and, like every link to Burnpedia, this plugin’s name and version; the plugin itself sends nothing when you click one. Each also names its screen (utm_content); Design a Pin and Pin it again with a new picture add the post’s title, permalink and from.

Every request to /api/v1 carries headers naming the plugin and its version; a Pin request also carries a random one-time key, so a retry never makes a second Pin. Only under a yes given since 1.0.46 to the install count below, each also says whether this site has used Pin older posts, and under which version of the words (see that paragraph).

Except the opt-in install count below (and the two headers it adds to these requests), no visitor data, no analytics, no usage statistics and no content beyond the fields above are transmitted, and the plugin has no telemetry of its own: it never reports your traffic, your other plugins, or anything about your visitors. Your site’s address is sent in items 3 to 9 above (as this site’s address, a post’s permalink or a picture’s address), in the Design a Pin and Pin it again with a new picture links, on the one-press connection screen if you use it, in a bug report if its box is ticked, and in the User-Agent of WordPress’s own More plugins request.

Your use of the service is covered by Burnpedia’s terms and privacy policy:

• Terms of service: https://burnpedia.app/terms
• Privacy policy: https://burnpedia.app/privacy

Pinterest itself is contacted by Burnpedia’s servers, not by your site; it downloads your image from your own site, so the image must be publicly reachable.

The install count (optional, off by default). WordPress.org does not tell
plugin authors how many sites run their plugin. If you switch this on under
Burnpedia → Connection, this site sends a short report:

• POST https://burnpedia.app/api/plugin-insights — once when you switch it on,
  then at most once a week while an administrator is using wp-admin, once if you
  deactivate the plugin, and once if you delete it. Sends exactly nine things: a
  random ID generated on this site, which plugin and which version, which of
  those four events it is, your WordPress version, your PHP version, your site
  language, whether this is a multisite network, and whether an API key is saved
  (true or false — never the key). Receives: nothing your site uses.
• One more answer, only while the count is on and an API key is saved: this
  site’s requests to /api/v1 carry a header saying whether you have used Pin
  older posts (used or unused, never which posts or how many) and one with the
  version of the words its yes was given under, so its tip email goes only to
  sites that have not. Switch the count off and the headers stop; Burnpedia forgets the answer the next time this site talks to it.
  A yes given before version 1.0.46 covers the count alone: this site’s requests to /api/v1 say nothing about Pin older posts until you choose Yes again on the Connection tab.

No install-count report carries your website address, not even in the
User-Agent header: the plugin sends its own. Switch the setting off and the ID is deleted, so counting
stops and a later change of mind cannot be joined to it. Nothing about any reader
or logged-in user is in it.

Report a bug and More plugins (only when you use them). Pressing Send report on Burnpedia → Report a bug sends POST https://burnpedia.app/api/plugin-bug-report: your description, an optional reply email, the plugin, WordPress and PHP versions, theme, language, whether it is multisite and whether a key is saved (never the key) — and your site’s address only if you tick “Include this site’s address” (it starts unticked). Opening Burnpedia → More plugins asks WordPress.org (https://api.wordpress.org/plugins/info/) for our plugin list via WordPress’s plugins_api(), as Plugins → Add New does. That request is WordPress’s own, so it carries WordPress’s usual User-Agent, which names this site.