Webhooks

Paste the HTTPS endpoint that should receive each new article. We send a JSON POST every time an article is published — for example https://yoursite.com/api/blog-webhook.

Add a Bearer token (at least 8 characters) so we can prove the request came from us. We send it as Authorization: Bearer <token> on every call — validate it in your endpoint before processing.

Send a test payload to confirm everything is wired up:

1. Click Send test request (also available as Publish first article on the connected screen)

2. Check your endpoint logs — you should see a POST with the article JSON

3. If you see a 200 response, you're good to go

Request Details:

• Method: POST

• Headers: Authorization: Bearer <your-webhook-secret>, Content-Type: application/json

Payload Example:

{
"id": 10,
"title": "Test Article for Webhook Integration",
"slug": "test-article-for-webhook-integration",
"metaDescription": "Test article to verify webhook integration is working correctly",
"content_html": "<h1>Test Article for Webhook Integration</h1>",
"heroImageUrl": "https://cdn.example.com/hero-image.jpg",
"content_markdown": "# Test Article for Webhook Integration",
"jsonLd": { "@context": "https://schema.org", "@type": "Article" },
"faqJsonLd": { "@context": "https://schema.org", "@type": "FAQPage" },
"languageCode": "en",
"publicUrl": "https://example.com/test-article-webhook",
"createdAt": "2025-03-20T03:41:18.570Z"
}

content_html can include embedded JSON-LD script tags. You also receive jsonLd and faqJsonLd as structured JSON fields for easier mapping.

Your endpoint should return HTTP 200 to acknowledge successful receipt.

On the Webhook saved screen, click Publish first article — we send your latest article to your endpoint to confirm the connection is live. After that, with Automatically Publish on (toggle at the top of the Integrations page), every new article is delivered automatically.

1. Go to your Content Plan and publish / re-publish any article

2. BabyLoveGrowth sends the article payload to your webhook URL
3. Check your endpoint logs and confirm it returns HTTP 200