Raw capture

Stores the exact request and response bodies odnoga exchanged with the vendor.

When to enable

• Debugging odd vendor behavior.
• Compliance / audit requirements.
• A/B analysis where you want to inspect full outputs.

When to disable

• Default state. Storage costs and PII exposure aren't worth it for steady-state.

Enable

Workspace → Cache card (raw capture sits next to cache because both are storage toggles) — or Workspace settings → raw_response_capture. Set a TTL (default 7 days).

Where it lands

one stored payload per request, joined by request_id. Visible in:

• Requests card → click a row → "Raw" tab.
• Super-admin Request Inspector with full diffing.

What's stored

• Full request body sent to the vendor (post-translation).
• Full response body returned by the vendor (incl. stream concatenation).
• Response headers from the vendor.
• HTTP status, byte counts.

What's not stored

• Your virtual key or vault keys (the row is keyed by api_key_id / vendor_key_index only).
• Vendor auth headers.