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.

Download Strapi package

Setup

  1. Download the integration package and add it to your Strapi project following the bundled README.
  2. Open Blogent in Strapi admin, select the target collection, explicitly map the required fields, and save.
  3. Copy the webhook URL and automatically generated authorization token shown in Strapi admin.
  4. 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.

The four actions your endpoint must support

  • inventory — list existing articles. Accept cursor and limit; return {articles: [snapshot], next_cursor: string|null}. A null cursor marks the last page.
  • read — read one article from the CMS. Accept target and/or content_id; return {article_snapshot: snapshot}. If native target IDs are supplied, use those IDs.
  • A snapshot contains identity, title, alias, date, article, target, revision, urls. Include the full content of every language, not just a summary. Use null for an unknown original date; URLs may be an empty map when unavailable.
  • create — publish a new article in every supplied language. The request includes a unique operation_id, a stable content_id, an empty target and null expected_revision. Return {posted:true,target,revision,urls} after saving.
  • update — update the article identified by target. Check expected_revision against its current version before writing. Keep its native IDs, URLs, aliases, original publication date, author and existing assets.
Universal webhook contract

Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.

Open webhook documentation

Test your connection

The test creates one article, reads it, updates it and reads it again. It compares every supplied language, full HTML, SEO fields, TOC and reading time. It leaves the test article on your website.

You can edit the JSON. The test adds a unique suffix to aliases to avoid overwriting an existing article. Add other languages or a real author_id if needed.

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.

Put your blog on autopilot

Connect your website and share what you know. Blogent takes it from there.