Command line

The same workspace as the application, from a terminal. Runs in CI without a display.

sendwire <command> [options]

Commands

run <name>

Run a suite, collection or folder in order.

--reporter <kind>	list (default), json, or junit.
--env <name>	Which environment to resolve {{variables}} from.
--out <file>	Write the report here instead of stdout.
--data <file>	CSV or JSON — runs once per row.
--bail	Stop at the first failing step.

Exits non-zero when any step or assertion fails, so it gates a build.

sendwire run "Checkout flow" \
  --env staging \
  --reporter junit \
  --out results.xml

  ok   Log in                142 ms
  ok     login worked
  ok   Create order          211 ms
  ok     order id captured
  ok   List orders            88 ms
  ok     status is active

  3 steps · 4 assertions · 441 ms
  all passed

send <request name>

Send one saved request. The body goes to stdout, so it pipes.

sendwire send "Get repository" | jq .stargazers_count

list [collection]

Show collections and the requests in them.

add-curl '<curl …>'

Import a cURL command as a request.

add-openapi <fileOrUrl>

Import an OpenAPI 3 document, grouped by tag.

--name <name>	Name the collection. Defaults to the spec title.
--only <a,b>	Import only these operations.
--dry-run	Show what would be imported, write nothing.

add-soap <wsdlUrl>

Import every SOAP operation as a collection. Same options as add-openapi.

where

Print the workspace path.

Data-driven runs

--data takes a CSV or JSON file and runs the suite once per row, with each column available as a variable.

user,plan
ada,pro
alan,free

sendwire run "Signup flow" --data users.csv --reporter json --out report.json

In CI

- run: sendwire run "Smoke tests" --env staging --reporter junit --out results.xml

Nothing to authenticate, no display needed, and the exit code is the result.