PulseTrace
Start free
All features
APIs

API monitoring with JSON assertions, auth and pre-request scripts

An API that returns 200 with the wrong body is still down. PulseTrace's HTTP monitors assert on status, headers, body text and JSON fields, carry authentication and pre-request scripts, and can be created in bulk from an OpenAPI spec.

Every HTTP monitor is an API check: choose the method, send headers and a body, and assert on what comes back — a status code, a header value, a JSON path equalling or containing a value, a maximum latency. Credentials live in the credential vault and are injected at check time, never stored in the monitor.

Pre-request scripts generate signatures and timestamps; on-demand executions let you run a check right now from the UI or the API and inspect the full request and response. For a whole API surface, paste the OpenAPI document and get a monitor per operation.

  • JSON assertions on any path, plus status, header, body and latency checks.
  • Auth — bearer, basic, API-key headers, HMAC via pre-request scripts.
  • OpenAPI import creates a monitor per operation.
  • gRPC unary checks via server reflection for gRPC services.
Start monitoring free Incidents in depth
incidents · live
checkout-api unreachable
downtime · 3 regions · opened 2m ago
Critical
TLS chain changed on cdn.acme.io
intelligence · acknowledged
Warning
db-replica latency recovered
anomaly · resolved automatically
Resolved

How it works

  1. 1Create an HTTP monitor (or import an OpenAPI spec for many at once).
  2. 2Add assertions, headers, a body and — if needed — a credential and a pre-request script.
  3. 3Probes run from each region; failed assertions open incidents with the response captured.

Plan availability

HTTP and gRPC monitors on every plan · credential vault and environments on Pro and above · OpenAPI import and the REST API on Team and above.

Compare plans →

Monitor types that use it

HTTP(S)gRPCMulti-Step API Test

Pairs with

OpenAPI import REST API PagerDuty

Questions about api monitoring

Can I assert on a nested JSON value?
Yes — assertions take a JSON path (for example data.items[0].status) and an operator: equals, contains, exists, greater/less than.
How are API keys and passwords stored?
In the credential vault, encrypted at rest and referenced by name from the monitor; they are injected at check time and never shown again after creation.
← DNS monitoringMulti-step API checks →