Webhook.
Publish blog content to any endpoint you control, with every delivery signed.
what it does
If your CMS isn't git-based and isn't HubSpot, register a webhook instead. On publish, ReachPill sends the full article — frontmatter fields, body and hero image URL — as a signed POST to your endpoint, and your side decides where it lands.
how it connects
Register your endpoint
Settings → Connections → Webhook: enter the HTTPS URL that should receive articles.
Save the signing secret
A per-organization secret is generated and shown once — store it. It's what your endpoint uses to verify a delivery actually came from ReachPill.
Verify the signature
Every request carries an X-Mediagen-Signature header (t=<unix seconds>,v1=<hex HMAC-SHA256>). Recompute the HMAC over the raw request body with your secret and compare.
what you get
- The complete article payload — frontmatter, body and hero image URL — in one POST
- HMAC-SHA256 signed deliveries, so your endpoint can reject anything that isn't really from ReachPill
- Works with any CMS or pipeline that can receive an HTTP POST