ReClaw webhook status and backup event delivery.

Use the SSE progress stream and documented backup API today; outbound webhooks will follow the same zero-knowledge backup event model.

Status

ReClaw does not currently emit outbound webhooks. The stable event surfaces are the authenticated backup API, the OpenAPI document, and the SSE progress stream.

Event Delivery

  • Use GET /api/backups/<backup-id>/events for in-flight backup status over Server-Sent Events.
  • Use GET /api/backups and GET /api/backups/<backup-id> for durable state.
  • Use /openapi.json for the canonical schema and error contract.

Planned Events

Future outbound webhook events are expected to mirror the backup lifecycle: backup.created, backup.uploaded, backup.finalized, backup.failed, backup.expired, and backup.deleted.

Security

Webhook payloads must never include backup passphrases, plaintext archive contents, or unwrapped encryption keys. ReClaw stores ciphertext and operational metadata only.