Integrations · WordPress
BlogPost publishes through the API that already comes with WordPress, using your username and an application password. No plugin. Here is what your WordPress needs, the step by step and what arrives with each post.
- No plugin: it uses WordPress’s own API
- Sign-up tests the connection with a draft and deletes it right away
- The post goes in published or as a draft, your choice
No card · 4 posts in total, on 1 site
What it needs
- WordPress 5.6 or later, with the site on HTTPS. Before that, the application password option doesn’t show up in your profile.
- A user who can publish posts and upload files. BlogPost publishes with that user’s access.
- The WordPress API (your site’s /wp-json address) responding. A security plugin or a Cloudflare rule that blocks it stops publishing; the sign-up test tells you.
Step by step
Create the application password
In the WordPress dashboard (yoursite.com/wp-admin), open your profile (Users, Profile) and scroll to Application Passwords. Name it BlogPost Automático and create it.
Copy it right away
WordPress shows the password only once, in a notice at the top of the screen. If it’s gone, revoke that password and create another with the same name.
Connect at sign-up
At BlogPost sign-up, enter your site address (no need for /wp-json), your WordPress username and the application password. The test creates a draft on your WordPress and deletes it right away.
Approve and publish
Every account starts with approval on: each article waits in the Approval tab of the dashboard. Once approved, it goes to WordPress published, or as a draft if you’d rather give the final click there.
What arrives
The whole post
Title, the text in HTML with the article’s formatting, excerpt and post address. It goes in as a regular post and uses your site’s theme.
The cover in the media library
The cover image goes to the media library and becomes the post’s featured image.
The tags
The article’s tags go onto the post. Tags that don’t exist in WordPress yet are created.
The real link
The address WordPress returns goes back to the dashboard, behind the Open button. BlogPost never builds a link on its own.
Limits
- Only the cover goes to the media library. Images in the middle of the text stay at their original address.
- It doesn’t install a plugin or change your theme: the post has your site’s look.
- Each subscription publishes to 1 site. Another WordPress site needs another subscription.
Other integrations
Wix
Site ID, member ID and API key: the Wix step by step.
Content API
For a developer-built site: the site key and the four reads.
All integrations
WordPress, Wix and the API side by side: what each one needs and what arrives.
Pricing
4 free posts to try it; then US$49/month or US$490/year.
No card · 4 posts in total, on 1 site
WordPressStraight answers
Questions about WordPress.
What people ask most before connecting WordPress to BlogPost.
Another question? Talk to the IATEC team on WhatsApp
No. BlogPost uses the REST API that already comes with WordPress, with your username and an application password.
No. It’s a separate password, created in your WordPress profile just for BlogPost to publish. To cut off access, revoke it in the same place; your login stays the same.
Check that the site is on HTTPS, that the password was copied in full and that /wp-json isn’t blocked by a security plugin or by Cloudflare. If you get stuck, the IATEC team helps on WhatsApp.
Yes. In the dashboard, in the Autopost tab, under External publishing, choose Draft: the approved post reaches WordPress unpublished, and you publish it from there.
The dashboard flags the post as not on the site, with the reason. In the Posts tab, the Send to site button tries again.