AI SEO blog for Strapi
The package adds one protected publishing endpoint to your Strapi project. It validates the incoming payload, checks the authorization header, downloads the cover into the Strapi media library and stores articles idempotently, so a repeated delivery updates the entry instead of duplicating it.
How to connect Blogent to Strapi
Strapi integration package
The ready package adds a protected Blogent publishing endpoint to your Strapi project: payload validation, authorization, image download to the media library, and idempotent article storage.
Setup
- Download the integration package and add it to your Strapi project following the bundled README.
- Open Blogent in Strapi admin, select the target collection, explicitly map the required fields, and save.
- Copy the webhook URL and automatically generated authorization token shown in Strapi admin.
- In the Blogent dashboard open Integrations → Strapi, paste the URL, set
Authorization: Bearer <token>, and run the connection test.
The connection test inventories existing content, creates one real article, reads its authenticated snapshot and updates the same native IDs. No public-page crawl is required.
Actions and stable identities
- Shopify, HubSpot, Webflow and Framer use the connected native publisher. WordPress, OpenCart, Strapi and Lovable use the installed Blogent connector; v0 and Replit adapt it to the existing app. Wix, Make, n8n and custom endpoints implement the synchronous contract; Zapier, Albato and ApiX-Drive use completion callbacks.
inventory: sendcursor: nullandlimit; return{articles: [snapshot], next_cursor: string|null}. Repeat the returned cursor until null.read: sendtargetand/orcontent_id; return{article_snapshot: snapshot}. Explicit nativetargetis authoritative. Blogent’s logicalcontent_idmay differ from the native identity.- Each snapshot contains
identity, title, alias, date, article, target, revision, urlsand optional image/author metadata.articlemaps locales to full title, alias, HTML, preview and SEO fields. Unknown original dates may be null and unavailable URLs may be an empty map. create: send the article payload, a uniqueoperation_id, logicalcontent_id, empty target and null expected revision. Return{posted:true,target,revision,urls}after complete publication.update: send existing native target IDs and the latestexpected_revision. Preserve original IDs, URLs/aliases, publication date, author and assets. Compare the revision atomically before applying changes.
Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.
Webhook tester
Run inventory, create, read and update on one real test article. Queued integrations wait for their completion callbacks.
What you get after connecting Strapi
- Publishing is idempotent: the same article delivered twice updates the existing entry rather than creating a second one.
- The cover is downloaded into the Strapi media library, so the article never depends on a temporary external URL.
- The plugin generates an authorization token in Strapi admin; Blogent sends it as
Authorization: Bearer <token>. - Payload validation rejects malformed deliveries at the edge instead of writing broken entries into your collection.
- The package ships with a README so a developer can add it to an existing project without reverse-engineering the contract.
- Blogent reads existing native articles and updates them with revision checks while preserving original IDs, URLs, dates, authors and assets.
Requirements and compatibility
- Platform
- A Strapi project you can deploy and add code to.
- Token
- Generated automatically on the Blogent page in Strapi admin.
- Endpoint
- A public webhook URL, for example
https://your-site.com/api/blogent/webhook. - Header
Authorization: Bearer <token>, using the token copied from Strapi admin.- Verification
- The connection test inventories existing content, creates one real article, reads its authenticated snapshot and updates the same native IDs. No public-page crawl is required.
Frequently asked questions about the Strapi integration
Do I need to write the integration myself?
No. The package contains the endpoint, validation, authorization, image download and storage logic. Add it to the project, configure the field mapping in Strapi admin and deploy.
What stops someone else from posting articles to my site?
The endpoint checks the generated token sent as Authorization: Bearer <token>. Requests without the correct token are rejected.
Will a retry create duplicate articles?
No. Storage is idempotent, so a repeated delivery of the same article updates the existing entry.
How do I check it works before going live?
Run the connection test from the Blogent dashboard. It publishes a real article with a unique alias through the same path as production content, so you can confirm it appears in your Strapi collection.
