How vgakilan/api-test works
api-test is a Windows PowerShell CLI for running configuration-driven API requests. The user selects an interface and environment, supplies optional overrides and payloads, and the CLI sends the request through curl.exe, checks the HTTP status, and displays redacted output; saving is optional. The graph reflects README-documented responsibilities and capabilities. Source excerpts were unavailable, so internal call ownership and unmentioned implementation details cannot be verified.
Main entry points: api.ps1 CLI entry point · Invoke-Curl.ps1 Curl execution · config.toml.example Configuration · .env.example Credentials
Components 15
Request Inputs
- Configuration
config.toml.example - Credentials
.env.example - Interface definitions
interface - Request payloads
interface/create-user/payloads/valid.json
Request Execution
- CLI entry point
api.ps1 - Config and payload helpers
lib/Common.ps1 - Curl execution
lib/Invoke-Curl.ps1
Results and Output
- HTTP status checks
lib/Invoke-Curl.ps1 - Output redaction
lib/Redaction.ps1 - Markdown reports
lib/Invoke-Curl.ps1
Other components
- CLI user
- curl.exe
- Target API
- Terminal output
- bat.exe
Connections 14
- CLI user → CLI entry point: runs
README.md - CLI user → Configuration: configures
README.md - CLI user → Credentials: sets credentials
README.md - CLI user → Interface definitions: selects interface
README.md - CLI user → Request payloads: supplies payload
README.md - CLI entry point → Config and payload helpers: uses helpers
README.md - CLI entry point → Curl execution: runs requests
README.md - Curl execution → curl.exe: executes
README.md - curl.exe → Target API: sends request
README.md - Curl execution → HTTP status checks: checks status
README.md - CLI entry point → Output redaction: sanitizes output
README.md - CLI entry point → Terminal output: displays results
README.md - CLI entry point → Markdown reports: saves optionally
README.md - CLI entry point → bat.exe: formats optionally
README.md