Inspectr supports a wide range of CLI flags to control how it captures, proxies, and exposes traffic. These options allow you to customize Inspectr to match your workflow.
Flag Type Default Description --listenstring :8080Address where Inspectr listens for HTTP requests --backendstring (none) Forward requests to this backend service --mock-backendstring (none) Serve mock responses from OpenAPI spec --mock-dynamicboolean falseGenerate dynamic mock data instead of static examples --catchboolean trueAccept and log requests without forwarding
Flag Type Default Description --appboolean trueEnable embedded Inspectr App UI --app-portstring 4004Port to serve the UI app --printboolean truePrint color-coded log output to the terminal
Flag Type Default Description --exposeboolean falseExpose Inspectr publicly via Ingress service --channelstring Subdomain to use on in-spectr.dev (e.g. my-api.in-spectr.dev) --channel-codestring Secret code required for remote access to the channel
Flag Type Default Description --auth-enabledboolean falseEnable API key authentication for proxied requests --auth-secretstring (none) Guard secret used to generate API keys --auth-token-ttlinteger 24Guard token expiration time in hours
Flag Type Default Description --apiSecretstring (none) Protect access to Inspectr’s admin API --store-pathstring .inspectr.dbPath to store request/response history --store-in-memoryboolean falseUse in-memory storage instead of persistent disk file
Flag Type Default Description --configstring .inspectr.yamlPath to YAML config file (overrides CLI flags) --versionPrint Inspectr version and exit
Flag Type Default Description --log-levelstring noneSet log verbosity (debug, info, warn, etc.) --http-timeoutinteger 30HTTP timeout in seconds for backend requests
inspectr --backend=http://localhost:3000
inspectr --catch=true --expose --channel=webhook-test --channel-code=secure123
inspectr --mock-backend=./openapi.yaml --mock-dynamic=true