IntegrationsWordPress, Wix and API
WordPress, Wix or a site built by your developer. The approved post goes to your site’s blog, on your domain and with your site’s look.
No card · 4 posts in total, on 1 site
WordPress
You connect it at sign-up
What it needs
Your username and an application password, created in your WordPress profile (it isn’t your login password). Requires HTTPS and WordPress 5.6 or later. No plugin.
What arrives
- Title, text and images
- Excerpt and post address
- Cover in the media library
- Tags, created if missing
Where it shows up
yoursite.com/post-title
Wix
You connect it at sign-up
What it needs
The site ID, the member ID and an API key from your Wix dashboard. If you get stuck, IATEC walks you through it on WhatsApp.
What arrives
- Title, subheadings, lists and links
- Inline images and cover
- Post excerpt
Where it shows up
yoursite.com/post/post-title
Developer-built site
Your developer connects it once
What it needs
A site key, generated in the portal and kept on the server. With it, your developer builds the post list, the post page and the sitemap, once.
What arrives
- Posts by language
- Full post: title, description, HTML, cover and tags
- Entries for your sitemap
Where it shows up
yoursite.com/blog/post-title
From draft to siteThe same path for all three
Connect and test
On WordPress and Wix, sign-up creates a test draft on your site and deletes it right away. On a developer-built site, they check the key with the connection test in the portal.
You approve
Each article waits in the Approval tab of the dashboard: you read it, adjust the title, description or text and publish. Every account starts this way; publishing straight away only happens if you turn it on.
It goes onto your site
Once approved, it goes to your site’s blog. On WordPress and Wix, you can also receive it as a draft and give the final click there.
For developersContent API
No WordPress and no plugin: your site fetches approved posts from a read-only API and builds the page its own way, at the path you choose.
On every routex-bpa-api-key: bpa_ck_…
GET/meSite, languages and blog pathGET/posts?locale=enPosts in that language, without the HTMLGET/posts/{locale}/{slug}The full post, with HTMLGET/sitemapEntries for your site’s sitemap.xml
- The key and the API address are in the portal settings.
- The key stays on the server, never in the browser. It isn’t the portal login: if the password changes, the blog stays up.
- Google reads your site’s sitemap.xml, not the API: merge the /sitemap entries with your pages.
IntegrationsStraight answers
Questions about connecting your site.
What each platform needs, what arrives and what changes between them.
Another question? Talk to the IATEC team on WhatsApp
No. BlogPost uses the API that already comes with WordPress, with your username and an application password. If a security plugin or Cloudflare blocks /wp-json, the sign-up test tells you and the team helps you unblock it.
Yes. On WordPress and Wix, it goes in as a regular post on your blog and uses your site’s theme. On a developer-built site, the site itself builds the page.
On WordPress, the whole text goes over, with the article’s formatting. On Wix, subheadings, lists, links and images arrive; bold, italics and tables aren’t converted yet, so it’s worth receiving it as a draft and checking it before publishing.
Yes. In the dashboard, choose to receive it as a draft: the approved post reaches WordPress or Wix unpublished, and you publish it from there.
If a developer looks after your site, they connect it once through the content API. If the site doesn’t exist yet, IATEC can build it.
No. WordPress, Wix and the API are in every plan, including the 4 free posts. Each subscription publishes to 1 site.
The IATEC team walks you through it on WhatsApp, step by step, until the sign-up test passes.