One endpoint — every article arrives as signed JSON.
Your app owns the rendering; DraftSEO owns the pipeline. Every publish fires a signed delivery to your endpoint — verify the HMAC, store the post, render it your way. Copy-paste receiver recipes exist for 16 frameworks, from Next.js to Rails.
| Connection | Webhook endpoint — a short receiver, recipe provided per framework |
|---|---|
| Security | HMAC-signed + timestamped — replay-window protected |
| Payload | Full article JSON — title, HTML, images, meta, slug, language |
| Sync | posts.list — reconcile your database against DraftSEO anytime |
| Framework lock-in | None — same contract for any stack |
Who does what
Paste the receiver for your framework, verify the signed test delivery, render posts from your store. After that: zero minutes per article.
You keep full control of markup, routing and caching.
Setup
Connect a site → pick your framework. You get a signing secret and an idiomatic receiver recipe.
~1 minute
Verify the HMAC signature and timestamp, then store the post — the recipe shows exactly how.
~10 minutes
DraftSEO sends a signed test event; green check = connected.
~1 minute
Every generated article arrives at your endpoint on schedule.
Ongoing · zero clicks
FAQ
The full article: title, HTML body, image URLs, SEO title and meta description, slug, language and more — everything you need to render it.
Every delivery carries an HMAC signature over a timestamped payload, with a replay window — your endpoint verifies it came from DraftSEO before accepting.
The payload includes image URLs from DraftSEO’s CDN; your system can rehost them on your own storage or serve them as-is.
No card required. Signed test delivery in under a minute.