Replay Log Entry
Re-fire a previously-logged request against the same endpoint. The platform reconstructs the original request from the log (method, path, headers, body sample) and sends it through the same routing path again. The replayed request is itself logged — the response includes the new log ID for follow-up analysis.
Use cases:
- Reproducing an upstream failure after deploying a fix.
- Walking through a CORS / auth issue with the agent's logs side-by-side.
- Testing the impact of a new traffic policy.
Idempotency is the caller's responsibility — replaying a POST /v1/payments/charge may double-charge. Limit replays to read-only operations or coordinate with the upstream first.
Path parameters
Request body
Optional — send an empty body or {} to replay the stored request unchanged.
30.original forces the stored request data and ignores any override fields above. Any other value is a modified replay and applies your overrides.Modified replays are plan-gated: any replay_type other than original requires the replay_with_modification entitlement (403 Forbidden without it). Replaying the stored request unchanged is available to all traffic_inspector holders.
Response (200 OK)
true on success (the request reached the agent). For replay-failed cases the call returns a 4xx/5xx error directly.Errors
traffic_inspector, or a modified replay (replay_type ≠ original) was requested without the replay_with_modification entitlement.