API Monitoring: Status Codes & Response Body Validation
Low-latency uptime monitoring with precise JSON schema validation and real-time alerting.
Configure API Check View DocumentationConfigure JSON Response Validation
Define exact HTTP status codes and validate nested JSON payloads to catch silent failures before your users do.
PingKit’s API checker supports custom request headers, payload matching, and schema drift detection. Set up a GET request to your /v2/payments endpoint and enforce a 200 OK status while verifying that data.status equals completed.
Request Configuration
Specify method, headers, and expected status range.
Method: POST
URL: https://api.example.com/v2/webhooks
Headers: Authorization: Bearer <token>, Content-Type: application/json
Expected Status: 200-204
JSON Body Assertion
Validate specific keys, types, and values within the response payload.
{ "status": "success", "timestamp": "{{ISO8601}}", "data": { "transaction_id": "{{string}}", "amount": "{{number}}", "currency": "USD" } }
Alert Configuration for Schema Drift
Automatically notify your engineering team when API responses deviate from the expected structure or return unexpected status codes.
Configure multi-channel alerts via Slack, PagerDuty, or email. Set custom thresholds for consecutive failures, response time degradation, or missing JSON keys. PingKit tracks schema versions and generates diff reports for every breaking change.
Status Code Rules
Define acceptable ranges and trigger alerts on specific error codes.
PrimaryAlert on: 4xx, 5xx
Cooldown: 5 minutes. Resolution requires 3 consecutive 200 OK responses.
Schema Validation Alerts
Detect type mismatches, missing fields, or value constraints.
SecondaryAlert on: type_mismatch, missing_key, value_out_of_range
Notify: #api-ops Slack channel + on-call engineer via PagerDuty.
Response Time Thresholds
Monitor latency alongside payload correctness.
TertiaryWarning: > 400ms | Critical: > 1200ms
Correlate with uptime checks to isolate backend vs. network issues.