Aglet

Verify direct webhook endpoint delivery

Endpoint verification should prove the configured URL receives the intended request directly or that every hop is explicitly reviewed. Test direct success, redirect, path rewrite, invalid target, and signature input. Inspect receipt and event identity after each case before accepting migration.

Check whether the outcome improved

  1. Define route outcomes

    Write expected URL, method, body, signature, acknowledgement, retry, and receipt for direct, reviewed redirect, changed method, wrong host, invalid target, and proxy rewrite. State which paths are unsupported. Keep the endpoint origin in every result.

  2. Run route fixtures

    Send synthetic events through each configuration and compare request bytes, headers, final host, verifier result, and receipt. Confirm a redirect cannot silently change the method or body and that unapproved targets stop.

  3. Check migration recovery

    Switch from old to canonical configuration in a bounded fixture, then inspect a retry and duplicate. Verify one event remains identifiable and side effects stay safe. Keep full payloads out of diagnostics.

What to carry forward

Accept when canonical delivery preserves method, body, signature, identity, and receipt, and redirects have an explicit disposition. Keep sender follow behavior partial if uncontrolled. Record route matrix, proxy revision, fixtures, and results. Record the destination actually reached for every redirect fixture and compare it with the approved migration route.

Technical background: Stripe documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow