Skip to main content
Future surface. Developer event streams, event names, webhook registration, signing, and delivery semantics are not available yet. The names below are illustrative, not a contract.
Actual plans two complementary delivery modes:
  • a resumable Job event stream for an active client; and
  • signed webhooks for server-to-server notifications.
Potential event families include Approval requests, Offer receipt, Evidence capture, Recovery, and successful Job Verification. Final event types will be published in the canonical OpenAPI contract before release.

​
Receiver requirements

Webhook consumers should be prepared to:
  1. verify the signature against the unmodified request body;
  2. reject stale or invalid signatures;
  3. deduplicate using the event ID;
  4. acknowledge quickly, then process asynchronously;
  5. tolerate duplicate and out-of-order delivery; and
  6. fetch the current Job projection before taking consequential action.
A webhook reports that Actual recorded an event. It does not independently prove an Outcome and cannot bypass Account authorization or Approval.
Do not implement signature verification from this page. The algorithm and SDK helpers will be documented when the webhook surface is released.
Last modified on August 13, 2026