Signed webhook integration

Bring Autopilot to your own publishing stack.

Connect Blogged to your application with signed article webhooks, a scoped Content API, image delivery, reviewed updates, and withdrawal receipts.

External publishing requires a paid content plan.

One connected workflow

  1. 1Create and review in Blogged
  2. 2Deliver to Signed webhook
  3. 3Verify the public article
  4. 4Review updates when content changes

Connecting a site does not change routing. Save destinations for new eligible articles when you are ready.

How Blogged works with Signed webhook

Build a receiver for Blogged's signed publishing contract to deliver approved articles into your application. Use the destination-scoped Content API when your server also needs to read approved releases.

Connect

Implement and verify the receiver contract, then store the shared signing secret on your server. Keep Content API keys server-side.

Publish

Handle publication, inspection, reviewed updates, and withdrawal. Preserve article identities and revisions so retries do not create duplicate posts or replace newer work.

Know the boundaries

An accepted request is still pending until publication is confirmed. External summaries are available only when your receiver supports noindex. A generic webhook URL alone is not a compatible integration.

What you need to connect

A public HTTPS receiver, durable storage, signature verification, image copying, and signed completion receipts. Developer setup is required.

Read the connection guide

Included with paid content plans

Publishing integrations require an eligible paid content plan. Free Projects and trials do not include external publishing. Provider fees and setup requirements may apply.

External delivery, summaries, and retries do not consume another Post. Existing content creation and review rules still apply.

Compare plans

Keep control after the first publish.

Reviewed updates

Inspect your CMS version before sending a reviewed update. Detected human edits require review; autosave does not overwrite the external copy.

Read the guide

Verified delivery

Follow delivery activity from pending to verified Live. Withdrawal tracks each managed copy until its removal is confirmed.

Read the guide

External website analytics

Collect consented visits and configured conversions for verified articles. Install tracking on your site; reporting is separate from hosted-blog analytics.

Read the guide

Content API and signed delivery

Read approved releases with destination-scoped server keys. Custom receivers preserve article identity, copy images, and confirm completion.

Read the guide

Signed webhook publishing questions

How does Blogged publish to Signed webhook?

Build a receiver for Blogged's signed publishing contract to deliver approved articles into your application. Use the destination-scoped Content API when your server also needs to read approved releases.

Is the Content API a substitute for a publishing receiver?

No. Reading approved releases does not confirm publication. Implement the signed delivery and withdrawal contract so Blogged can verify the public article and expose its summary links.

Can I review changes before updating my CMS?

Yes. Save your working copy in Blogged and inspect the external version before publishing a reviewed update. Detected CMS edits require review. Importing supported CMS text does not import advanced widgets or CMS images, and existing Autopilot authority still applies.

Is external publishing included in the Free Project or trial?

Publishing integrations require an eligible paid content plan. Free Projects and trials do not include external publishing. Provider fees and setup requirements may apply.

Will connecting a CMS move my existing articles?

No. Connecting alone does not change publishing. Save your destinations to route new eligible articles. Existing drafts and published articles keep their existing destination.

Do integrations use additional Post allowance?

External deliveries, summaries, and retries do not consume another Post. Article creation keeps its existing allowance and billing rules. CMS hosting and provider fees are separate.

The workflow behind your publishing.