API / HTTP monitoring

Validate the response—not only the connection.

Use advanced Website monitor configuration to model an API request, define success, and retain the evidence when an endpoint returns the wrong result.

Start monitoring Read the documentation

HTTP requestIllustrative setup

POST https://api.example.test/health

Headers: Accept: application/json
Request body: {"probe":"checkout"}
Expected status: 200
Response rule: Contains “ready”

Model the request

Choose a supported method, headers, and optional body.

Define success

Require an expected status and eligible content rules.

Track performance

Retain response timing beside success and failure.

Investigate failure

Connect each result with incidents and recovery.

01Request builder

Send the request your endpoint expects.

Advanced HTTP configuration extends the existing Website monitor rather than creating a disconnected monitor type. Sensitive headers and bodies stay inside the authenticated workspace.

Request and validationPingBeacons

POST /v1/checkout/health

Authorization: Bearer ••••••••
Content-Type: application/json

{"probe":"checkout"}

Response · 184 ms200 · contains “ready”

02Response validation

A reachable endpoint can still be wrong.

Expected status codes and contains or does-not-contain rules let PingBeacons evaluate whether the returned response represents a healthy service.

Supported HTTP methods
Structured request headers
Optional request body
Contains and does-not-contain rules

Monitor configurationPingBeacons

GEThttps://service.example.test/health

Check interval5 minutes

Expected status200 OK

Response must containok

Alert contactsOperations

Latest check200 OK · 184 msHealthy

03History

Keep request outcomes and timing together.

Retained checks show response status, timing, and failure context, so investigation starts with evidence rather than the latest state alone.

Check historyPingBeacons

14:08:02200 OK184 ms

14:03:02200 OK206 ms

13:58:01503412 ms

04Operations

Turn validation failure into an operational record.

Failed API checks use the same incident, notification, maintenance, reporting, and recovery workflows as other HTTP monitors.

Incident lifecyclePingBeacons

14:02Healthy request

14:04Failed check

14:04Incident opened

14:05Notification sent

14:08Recovery recorded

Start with PingBeacons

Know when an endpoint stops behaving as expected.

Model the request, validate the response, and keep every retained result connected to operations.

Start monitoring Explore features