endpoint-validator

Automating API endpoint health checks in a CI/CD pipeline requires a validator that reads endpoint definitions, tests response status and timing, and outputs machine-readable results with CI-friendly exit codes. This approach gates deployments by detecting API health issues before release.

Deterministic API smoke tests run by validating endpoint responses and timing against a centralized definitions file. This process uses a Discover-Validate-Report workflow to ensure consistent pre-deployment validation and outputs structured data suitable for automated pipelines.

Validating specific JSON keys in an API response during automated testing is handled by configuring optional JSON key checks within your endpoint definitions. The validator tests each endpoint for status, timing, and the presence of those specified keys.

Testing mutating API endpoints safely in an automated validation pipeline is supported by enforcing read-only GET requests by default. Explicit enablement is required for mutations, ensuring safe defaults while reporting security header presence as warnings.

Configuring endpoint validation requires creating an endpoints.json file in your project root. This centralized file defines the base_url and the specific endpoints to test, allowing the validator to discover and execute checks automatically.