Combined preproduction API test
39-combined-preprod.yaml
HTTP(S)
What this example does
This example demonstrates combined preproduction api test.
Checks and behavior
- Sends an GET request to https://api.example.invalid/health.
- Checks allowed/denied HTTP status codes.
- Validates required, forbidden or matching HTTP headers.
- Looks for expected response content and/or rejects known error markers.
- Inspects structured JSON response values.
- TLS settings cover certificate trust, certificate expiry.
Adapt example domains, addresses, credentials and thresholds to your environment before use.
YAML configuration
# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
name: Combined preproduction API test
url: https://api.example.invalid/health
connection:
resolve:
api.example.invalid: 10.20.30.40
request:
method: GET
user_agent: httptest/2.0
follow_redirects: false
headers:
Accept: application/json
auth:
type: bearer
token_env: HTTPTEST_API_TOKEN
timeouts:
connect: 3
response: 10
tls:
verify: true
min_valid_days: 14
min_version: TLSv1.2
certificate:
san_contains: [api.example.invalid]
cipher:
deny: [AES128-SHA]
tests:
status:
allow: [200]
headers:
exists: [Content-Type]
absent: [X-Debug]
body:
not_contains: [traceback, exception]
response:
min_bytes: 10
max_bytes: 65536
content_type: application/json
json:
paths:
- path: status
equals: healthy