webhooks

Outbound webhooks: per-subject endpoints, HMAC-signed POSTs, backoff, dead letters and replay.

With cargo

cargo add cratefield-module-webhooks

What it is

webhooks.

Outbound webhook delivery, as a module. A venture's customer registers one endpoint per subject — their account id, their tenant id — with an optional event-type filter, and receives a signed POST for every published event the filter matches. Delivery rides the core Outbox: durable exactly when the event that caused it is, retried with exponential backoff, dead-lettered after repeated failures, and replayable by hand.

From the crate’s own README.

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 5 versions recorded, newest first. Every published version is on crates.io.

  1. 0.4.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
  2. 0.4.1

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
3 earlier versions 0.2.1 to 0.4.0
  1. 0.4.0

    crates.ioReleaseDiff

    Other

    • deliver within the per-module ScheduledBudget via Outbox::drain_within (#554) (#736)
  2. 0.3.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).

    Other

    • updated the following local packages: cratefield-core
  3. 0.2.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

One of 76 crates in the harness, all of them MIT and all of them in one repository.