API and response validators

Use these when the failure is in the payload or HTTP envelope you already have: SOAP Fault vs Body, webhook JSON, JWT exp/nbf, or a GraphQL query that will not parse. They do not replace a full REST client for status codes and latency — see the /api section for webhook tester and live GET checks.

Signature and replay tools check HMAC-style headers and timestamp windows. CORS preflight, Link, ETag, and Content-Type helpers inspect headers, not business logic. OpenAPI and GraphQL linters are syntax/structure only, not full spec conformance.

Response & webhook bodies(3)

SOAP(1)

Auth, signatures & replay(3)

HTTP mechanics(6)

OpenAPI & GraphQL(2)

FAQ

JSON from curl still fails here?
Strip the HTTP status line and headers, or use API Response Checker which splits on the blank line then validates JSON. Non-JSON APIs will always fail this path — use SOAP or XML tools instead.
Does JWT Claims Inspector verify signatures?
It decodes header and payload and checks exp/nbf/iat. It does not verify JWS with a key. Use that for debugging claims, not for auth decisions.

Other validator groups