Inspect event content
Read the original body without changing the captured event or executing its contents.
Search before opening an event
On Events, typing a query searches metadata and retained text content by default across the selected organization. You do not need to open each body first. Search matches literal text without regard to case; JSON, XML, plain text and URL-encoded form content are searched in their original text representation. Compressed, multipart, binary or unsupported encodings are skipped; text must be UTF-8. Queries are limited to 256 UTF-8 bytes.
Results arrive in bounded pages. Continue search checks more history; the counters show events and bodies checked and content skipped because it expired, was not retained or is unsupported. A partial or failed search is not proof that no matching event exists. Search again starts a fresh scan. Clearing the query returns to the paginated event history.
Results contain metadata only, without body excerpts. Search terms and matches stay in this page and clear when you switch organizations, leave the page or sign out. Content matches are removed and the search refreshes when their retention expires. Source detail, Live and the command palette keep their existing metadata search behavior.
Open the Request detail
When the Request detail is open, retained content loads for the selected event and organization. Closing the detail or leaving the section clears it. Lists and Live stream metadata only; opening another event starts a separate scoped read.
The backend checks event-read permission, including viewers, and responds with no-store. A failed read offers Retry; a failure is not silently converted into an empty body.
Formatted and Original
Formatted is a reading aid. Original shows the unchanged representation; Copy original copies the full original text, or base64 for binary content. Formatting does not update the stored body/hash, delivery or signature.
The preview is limited to 128 Ki characters. Formatting also has token and nesting limits; larger or complex input falls back safely. The preview limit does not truncate what Copy original copies.
- JSON media types, including +json: indentation preserves numeric tokens, duplicate keys and string contents rather than converting them through JavaScript values.
- XML media types, including +xml: conservative formatting for supported markup. Mixed content and xml:space retain significant spacing; DTD/entity input falls back to original text.
- application/x-www-form-urlencoded: pairs can appear on separate lines without decoding or altering their original encoding.
- Malformed or unsupported text uses the original view. HTML remains inert text, never a rendered page.
- Binary bytes or unsupported character encodings are represented as base64. A zero-byte available body is distinct from unavailable content.
Expiry and access changes
Content expires 30 days after original receipt. The view clears and replay becomes unavailable when that deadline is reached. Switching event/organization, logout, denied access or closing the section clears content and discards stale responses.
expired means the original retention elapsed. not_retained means there is no retained body, including historical events already purged. Neither state is a body of zero bytes. The interface cannot restore historical content.
Headers and delivery
Displayed headers are filtered metadata, not a complete set of inbound credentials. The original delivery block describes its state, attempts, recorded HTTP result and ambiguity. Reading the body does not mean a delivery is eligible.
No private content is put into the shared event cache, raw-payload diff or cURL generator. Copying content is an explicit user action; handle the copied data according to your organization’s policy.