Every CLI webhook endpoint, and every tunnel unless you pass --no-log, captures its requests to a local JSONL file at ~/.otterkit/requests/<subdomain>.jsonl, one JSON object per line. Each entry has the timestamp, method, path, headers, body (base64), response status, and duration.
Read captured requests with the inspect command:
# Pretty-print the last 20 requests
npx otterkit inspect hook-a1b2c3d4
# Raw JSONL output (pipe it to jq and friends)
npx otterkit inspect hook-a1b2c3d4 --json
# Show the last 50 requests
npx otterkit inspect hook-a1b2c3d4 --last 50
# Live-tail new requests as they arrive (Ctrl+C to stop)
npx otterkit inspect hook-a1b2c3d4 --follow
# Filter by method, status (exact or class), and path substring
npx otterkit inspect hook-a1b2c3d4 --method POST --status 5xx --path /webhook
# Export as HAR 1.2 for browser devtools or any HAR viewer
npx otterkit inspect hook-a1b2c3d4 --har > capture.harFilters combine, and they work with --json, --follow, and --har. --status takes an exact code such as 500 or a class such as 5xx. The JSONL format also works with standard tools like jq, tail -f, and grep.
How long logs are kept#
Stopping a session keeps its log, so you can still inspect and replay what it received. The CLI keeps logs for ended sessions for 7 days, up to the 20 most recent, then deletes them. otterkit down deletes the logs of the profiles it stops.
Cloud endpoints created in the console store history on the server instead. Read it with otterkit requests; see Server-side history.