Inspect¶
The other sections find what is wrong. These commands open one request, read inside bodies, turn a capture into data, and package a result for another person or another tool.
| Command | What it does | Page |
|---|---|---|
show-entry |
Prints one request and response in full, with secrets masked | Show an entry |
search |
Finds text inside request and response bodies | Search bodies |
extract |
Pulls one JSON field out of every body | Extract a field |
export |
Flattens every entry into one NDJSON or CSV row | Export |
report |
Writes a markdown summary for a ticket or a document | Report |
curl |
Writes a masked curl command that repeats a request |
curl |
handoff |
Writes what a backend team needs to find the failing calls | Handoff |
Before you share anything¶
These commands exist to produce output you can hand to someone else, so what they mask matters. WireTrail masks a
fixed set of headers, a fixed set of JSON keys, and values that look like random tokens. It does not mask a
credential it does not recognize. Two of these commands, search and extract, mask less than the others.
How redaction works lists what each command does, and
Handle captures safely says how to check before you send.
Recipes¶
- Hand a failure to the backend team builds a ticket from a failing call.
Related¶
- Failures finds the requests worth inspecting.
- JSON output for the structured form of each result.