Waslوصل

Every delivery.
A verifiable trace.
Signed webhooks sent to a controlled HTTP receiver, with persistent attempts, receipt deduplication and bounded retry recovery.

Disciplines
HTTP / HMAC-SHA256 / Persistent delivery state
Provenance
Independent studio project
Year
2026
Demo
Live · synthetic data
Wasl application with synthetic records, captured during local verification
01

The brief

An event can arrive twice, fail signature checks or meet a temporarily unavailable destination. Each outcome needs a clear, testable response.

02

The approach

Wasl signs each delivery attempt, validates the body and timestamp at the receiver, persists receipts and records response codes. Deliberate receiver failures expose retry behavior.

03

What you can verify

  1. Send a valid event and inspect its HTTP receipt.
  2. Reject an invalid signature or expired timestamp.
  3. Trigger a temporary failure, retry and see the successful receipt.
  4. Follow permanent failure to its three-attempt limit.
  5. Inspect persisted attempts, idempotency and interrupted-delivery recovery.
04

Implementation & handoff

A live sender and receiver with durable event state, three-attempt limit, expiring delivery leases and recovery for interrupted attempts. Tests include invalid signatures, delayed retries and receipt integrity.

05

Honest context

A controlled integration lab on this site. Failure scenarios are intentional and retries are manually triggered. No external provider account, background scheduler, email delivery or security certification is claimed.