HTTP / REST endpoint
Point at any evidence-producing JSON API: base URL + auth header + read-only endpoints with JSON-path assertions. Each endpoint becomes evidence.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Endpoint reachable and returns 2xx
- GET endpoints and read-only POST query endpoints
- JSON-path assertions (equals / contains / exists / >= / <=)
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL
- Endpoints (JSON)
- Auth header name
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
HTTP / REST endpoint evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in HTTP / REST endpoint evidence
Get a guided demo, or start by scanning any domain for free.