Acklane documentation
Configure an active source, follow incoming events and inspect the outcome of each delivery.
The workflow
- Create a source with optional signature validation and a destination you control.
- Copy the ingress URL shown by your installation; do not construct it from a sample hostname.
- Use Live and event history for captured metadata, then open an event to inspect its signature, available content and original delivery.
- For retained, eligible content, confirm a replay to the source’s current destination and track its separate delivery history.
What acceptance means
With async capture enabled, an accepted 202 follows the transaction that stores the event and delivery work. It does not confirm a successful request at the destination or a business outcome. A paused source may acknowledge with dropped:true instead of storing an event.
Async capture is disabled by default. Without it, Acklane captures metadata without retained body or delivery jobs. Enabling it is an operator configuration decision.
Content and identity
New accepted async events retain encrypted bodies for 30 days from receipt. Availability is separate from signature validity and delivery eligibility. Historical bodies already purged cannot be reconstructed.
Outbound x-acklane-id identifies the captured event, including retries and deliberate replays. A replay has a new job; duplicate processing remains possible at the receiver.