await blocks until a request matching your filters arrives on a capture log, then prints it. It is the scriptable building block for CI and agents: trigger the event, wait for it to arrive, then check the payload. By default it keeps streaming matches. The session it watches keeps running either way, because await only reads the log and never stops the tunnel or endpoint behind it.
# Stream every incoming request (Ctrl+C to stop)
npx otterkit await hook-a1b2c3d4
# CI: exit 0 as soon as the webhook lands, exit 2 if it doesn't within 2 minutes
npx otterkit await hook-a1b2c3d4 --count 1 --timeout 120s --json
# Filters combine, like inspect's
npx otterkit await hook-a1b2c3d4 --method POST --path /stripe --status 2xx| Flag | Meaning |
|---|---|
--method <method> | Match only this HTTP method (EMAIL for inbox messages). |
--path <substring> | Match only paths that contain this. |
--status <status> | Match only this response status, e.g. 500 or 5xx. |
--count <n> | Exit with code 0 after N matches. Default: keep streaming. |
--timeout <duration> | Give up after e.g. 30s, 5m, or 2h, with exit code 2. |
--json | Print each match as one JSON line. |
With --json each match prints as one JSON line, so an agent can pipe the payload straight into the next step. Exit codes are predictable: 0 once --count is met (or on Ctrl+C), and 2 when --timeout expires first.