PayloadCanary

API response monitoring

Monitor more than API uptime.

Turn the API checks you repeat manually into scheduled monitors. PayloadCanary runs GET requests and checks the response against the rules you define.

Start monitoring Log in

For engineering, integration and API support teams.

Illustrative monitor result · Synthetic example

Latest stored result

Catalog freshness

FAILING

GET · Scheduled run

HTTP status
200
Latency
184 ms
JSON parsing
Parsed

Configured checks

  • Status codePASS
  • Array not emptyPASS
  • Timestamp freshnessFAIL

The endpoint responded. A configured freshness check failed.

Stored check outcomes, not a live health claim.

Beyond the connection

A response is only the first check.

A reachable API can still return an empty array or stale data. Define the checks that matter to your workflow.

Basic uptime check

“Did the endpoint respond?”

  • Request completed
  • HTTP status returned

PayloadCanary

“Did the response meet my configured checks?”

  • Expected status and latency limit
  • Required JSON paths and non-null values
  • Populated arrays and minimum record counts
  • Timestamps within your freshness limit

PASSING / FAILING reflects configured check evaluation. HTTP 2xx alone does not mean PASSING; a non-2xx response can pass when it matches your expectation.

From manual check to monitor

How it works

  1. Configure the request

    Set the endpoint, request headers, query parameters and timeout. Use GET or send a JSON body with POST.

  2. Define the checks

    Choose the status, latency and JSON data rules that describe an acceptable response for your use case.

  3. Run it. Review the result.

    Enabled GET monitors run on a schedule and record results. POST execution is manual-only today. Manual GET runs are also available.

Checks you can use today

Be specific about an acceptable response.

Expected status code

Require the HTTP status you configure, including an expected non-2xx response.

Maximum latency

Check that response latency stays within your configured limit.

JSON path exists

Check that a JSONPath expression finds at least one match.

Not null

Require matching JSON values to be non-null.

Array not empty

Require each matched value to be an array with at least one item.

Minimum record count

Require each matched array to contain at least the number of items you set.

Timestamp freshness

Check that matched timestamps are within your maximum age and are not in the future.

Your request configuration

API key, Bearer token and custom-header authentication through request headers. Query parameters, JSON POST bodies and configurable timeouts.

Evidence for investigation

Review run history, HTTP status, latency and JSON parsing state. Disable a monitor to pause execution while retaining its history.

Email failure alerts

Scheduled failures can notify the workspace owner by email. Continued failures are throttled; scheduled recovery sends a recovery email. Manual runs do not send alerts.

Monthly plans

Choose the capacity you need.

The same checks across every plan. All prices in USD, billed monthly.

Create your account, then choose a plan in Billing. An active subscription and an available monitor slot are required to create a monitor. Activation follows Stripe confirmation.

Operational evidence. Private configuration.

Operational result views keep endpoint URLs, request headers and request bodies out of the presentation. Review check outcomes without displaying sensitive request configuration.

Put your repeat checks to work

Make your next API check a monitor.

For SaaS APIs, data feeds and the integrations your team supports.

Start monitoring