Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Webhook replay API: Design and governance for manual reprocessing
A replay API lets you resend webhook events in a controlled way. This guide covers authentication, filtering, audit logs and governance for safe manual reprocessing.
Quick answer
A replay API enables targeted resending of webhook events after failures or misprocessing. Key elements are strict authentication, precise filters, immutable audit logs and clear governance. In practice, combine token‑based auth with roles, event IDs, time filters and auditable logs to ensure security and traceability.
Why you need a replay API
Receivers fail, process events incorrectly or introduce bugs. A replay API lets you resend only the affected events instead of restarting systems or notifying customers manually. For Swiss operations in Zurich, Geneva or Bern, targeted replays cut effort and downtime.
Basic security requirements
Security is paramount. Use strong authentication (OAuth2 client credentials or short‑lived JWTs). Limit replay permissions by role. Enforce TLS and validate original event signatures before replays so receivers can reject forged data.
Authentication and authorization
Separate machine access and operator access. Machines use OAuth2 clients with limited scopes (e.g. replay:read, replay:write). Humans use a console with 2FA and short sessions. Roles (Viewer, Operator, Auditor, Admin) control allowed filters, time windows and target endpoints.
Filtering and selecting events
Provide precise, reproducible filters: event ID, type, time window, status (failed, delivered), payload fields and recipient ID. Include a preview that shows payload hashes before a replay runs. Limit events per replay and support batched jobs with pagination.
Audit logs and traceability
Every replay must be auditable. Log who (user/client), when, which event IDs, target endpoints, number of attempts and HTTP results. Store immutable payload hashes and signatures so integrity checks are possible. Keep logs searchable in ELK or a SIEM.
Governance and operating rules
Define processes: require approvals above a threshold, escalate repeated failures, and set retention policies for replay records. Set review SLAs, publish limits to customers in Switzerland and handle personal data carefully—mask or exclude PII where required.
Frequently asked questions
How do I prevent misuse of the replay API?
Combine short token lifetimes, role‑based scopes, rate limits and approval workflows. Audit logs and anomaly alerts help detect suspicious replay patterns early.
Which filters matter most?
Event ID, time window, status (failed/delivered), recipient ID and payload attributes. These filters let you target replays precisely and avoid side effects.
How long should I keep replay logs?
Operationally, keep at least 90 days for debugging. Compliance needs may require longer retention. Mask personal data where possible.
Can replays disrupt recipients?
Yes. Provide previews, idempotency headers or replay markers, and coordinate with receivers so repeated events are handled safely.