sreq run

Make HTTP requests with automatic credential resolution.

Synopsis

sreq run <METHOD> <path> [flags]

Description

The run command is the core of sreq. It resolves credentials from configured providers and makes authenticated HTTP requests.

Arguments

Argument	Description	Required
`METHOD`	HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS)	Yes
`path`	Request path (e.g., `/api/v1/users`)	Yes

Flags

Flag	Short	Description	Default
`--service`	`-s`	Service name	—
`--env`	`-e`	Environment	`dev`
`--data`	`-d`	Request body (or @filename)	—
`--header`	`-H`	Add header (repeatable)	—
`--output`	`-o`	Output format: `json`, `raw`, `headers`	`json`
`--timeout`		Request timeout	`30s`
`--offline`		Use cached credentials only	`false`
`--no-cache`		Skip cache, fetch fresh credentials	`false`
`--verbose`	`-v`	Show detailed output	`false`
`--dry-run`		Preview without executing	`false`

Examples

Basic GET Request

sreq run GET /api/v1/users -s auth-service -e dev

POST with JSON Body

sreq run POST /api/v1/users -s auth-service -e dev \
  -d '{"name": "John Doe", "email": "john@example.com"}'

POST with Body from File

sreq run POST /api/v1/users -s auth-service -d @payload.json

Custom Headers

sreq run GET /api/v1/users -s auth-service \
  -H "X-Request-ID: abc123" \
  -H "Accept: application/json"

Verbose Mode

See what sreq is doing under the hood:

sreq run GET /api/v1/users -s auth-service -v

Output:

Request Details:
  Service:     auth-service
  Environment: dev
  Method:      GET
  Path:        /api/v1/users

Resolving credentials from providers...
  Base URL:  https://auth.example.com
  Username:  api_user
  Password:  ap****rd

{"users": [...]}

Dry Run

Preview what would be sent without executing:

sreq run POST /api/v1/users -s auth-service --dry-run

Different Output Formats

# Pretty-printed JSON (default)
sreq run GET /api -s auth -o json

# Raw response body
sreq run GET /api -s auth -o raw

# Include response headers
sreq run GET /api -s auth -o headers

Offline Mode

Use cached credentials without network access:

# First, cache credentials
sreq sync dev

# Then use offline
sreq run GET /api -s auth --offline

Using Contexts

# Use a named context
sreq run GET /api -s auth -c production

# Override context values
sreq run GET /api -s auth -c production -e staging

Request Flow

Load configuration from ~/.sreq/config.yaml
Resolve context (from -c flag or default_context)
Check credential cache (unless --no-cache)
If not cached, fetch from providers (Consul, AWS, etc.)
Cache credentials for next time
Make HTTP request with resolved credentials
Save to history (unless SREQ_NO_HISTORY=1)
Display response