Feedjoltdocs
Integrations

Webhooks

Feedjolt POSTs signed events to your endpoint when posts, statuses, comments, or votes change. Set up endpoints, pick events, and replay from the delivery log.

When something happens in Feedjolt - a post is created, a status changes, a vote crosses a threshold - Feedjolt can POST to a URL you control.

This page covers the admin setup. For the engineer-oriented reference (payload shapes, signature verification, retry behaviour), see Developers -> Webhooks.

Set up an endpoint

  1. Dashboard -> Settings -> Webhooks -> New endpoint.
  2. Enter your URL.
  3. Pick which events to send.
  4. We generate a signing secret. Save it; you'll use it to verify incoming requests.

Events

Pick any subset per endpoint. You can have multiple endpoints with different event filters.

EventWhen
post.createdA new post is created on a board you're subscribed to.
post.mergedA post is merged into another.
post.moderatedA draft post is approved or rejected.
status.changedA post moves between statuses.
comment.createdA new comment is posted.
vote.thresholdA post crosses a configured vote count.

Delivery contract

  • POST application/json with the event payload as the body.
  • Headers: X-Feedjolt-Signature (HMAC-SHA256 over the canonical body), X-Feedjolt-Event, X-Feedjolt-Timestamp.
  • 10-second timeout.
  • One delivery attempt per event today. Failures are logged; admins can replay manually from the dashboard.

Full payload shapes and signing examples live in Developers -> Webhooks.

Delivery log

Every attempt is logged at Settings -> Webhooks -> [endpoint] -> Deliveries:

  • Event, timestamp, response code, response body (capped at 4 KB).
  • Replay button to re-send the same event on demand.

Logs are retained while we figure out a sensible TTL - assume "until the table gets large enough that we add one".

Best practices

  • Respond 2xx in under 10 seconds. Queue heavy work; ack fast.
  • Be idempotent. Manual replays send the same event again.
  • Verify signatures. Without verification, anyone on the internet can forge events.

See the developer reference for code examples in Node, Python, Ruby, and Go.

On this page