Reading the request trace
Every request a twin received, with bodies and headers.
Each twin records every request it served, at /veris/requests.
veris sandbox trace --limit 20That merges every twin’s trace into one table. --service <twin> narrows it to a
single twin, --body <id> prints one entry’s headers and bodies, and --follow
tails the trace as requests arrive.
$CONTROL_URL is the twin’s control URL, printed by veris sandbox services get <twin>.
curl "$CONTROL_URL/veris/requests?limit=20" | jq '.requests[] | {method, path, status}'Newest first. ?order=asc reverses the order. ?limit= accepts up to 1000. The
rest of the twin’s routes are in
the /veris/* control plane.
Each entry carries the method, path, status, both request and response bodies, and both sides’ headers.
Query strings are not recorded. An assertion that depends on query parameters has to read them from your own client’s logs.
Filtering by tier
veris sandbox trace --tier handlercurl "$CONTROL_URL/veris/requests?tier=handler"| Tier | Returns |
|---|---|
handler | Traffic your application sent |
fault | Exchanges an armed fault produced |
control | Your own /veris/* seeding and read-back calls |
delivery | Callbacks the twin sent out to your application |
control traffic is recorded like any other. After a heavy seed an unfiltered
page is mostly your own writes. Use the handler tier to see what your code sent.
Redaction
Credentials, cookies, OAuth codes and private keys are [REDACTED], as is any
header whose name contains token, secret, signature, password or key.
Idempotency headers stay visible.
What a status means
Read the trace before attributing a failure to the twin, and reproduce with
curl to confirm.
| What you see | What it means |
|---|---|
A vendor-shaped 4xx | Usually the real error for the request you sent. Read the body |
A refusal naming itself unsupported, usually 501 | Conclusive. That operation is not modelled |
An ordinary 400 or 404 | Inconclusive. The vendor sends these too. Check credentials, API version, payload shape and seeded rows |
A bare 500 | A defect. Capture the request and the trace entry and report it |
Repeated 502 | Check whether the sandbox is alive and inside its TTL |
| A timeout | Check for an armed latency or hang, and whether the request reached the trace |
In the console
The sandbox page has a Requests tab per twin.