Webhook

When you approve a publish, BirchSeek POSTs the article as JSON to an HTTPS endpoint you control, signed with an HMAC-SHA256 of the timestamp and the raw body. Use it for any platform without a dedicated connector.

What BirchSeek does

• POSTs a JSON payload with the article's title, slug, markdown body, meta fields, tags, and FAQ pairs
• Signs every delivery: X-BirchSeek-Signature: t={timestamp},v1={hmac-sha256}, where the HMAC covers the timestamp and the raw body joined by a dot - the same scheme Stripe uses
• Sends a unique X-BirchSeek-Delivery-Id so retries are safely idempotent on your side
• Retries a failed delivery at 1 minute, 5, 30, 2 hours and 6, then marks it dead - and shows you every delivery receipt
• Lets you fire a signed sample payload any time to test your endpoint

Setup

1. 01

   Stand up an HTTPS endpoint

   Any URL that accepts a POST with a JSON body and answers 2xx within 30 seconds. HTTPS is required; plain HTTP endpoints are rejected.

2. 02

   Add the endpoint in BirchSeek and copy your signing secret

   Choose Webhook in the connector setup, enter the URL, and generate the signing secret. It's shown exactly once - store it in your secret manager. You'll use it to verify the signature header on every delivery.

   On screen: The connector form with the endpoint URL field and a one-time secret reveal beginning with whsec_, with a copy button and the warning that it won't be shown again.

3. 03

   Verify signatures and send a test

   Recompute the HMAC over the signature's own timestamp, a dot, and the raw body, compare in constant time, and reject stale timestamps (code samples are in the webhook reference). Then use Send a test: BirchSeek fires a signed sample payload and reports your endpoint's response status.

   On screen: A test result panel confirming the HTTP status your endpoint returned.

The payload schema, verification samples, and the retry schedule are in the webhook reference below.

Webhook reference↗