API monitoring that understands your responses.

A 200 status is not proof that your API works. UptimePush inspects the JSON, measures latency and alerts on the channel your on-call team actually reads.

Assert on the response, not only the status

Point a monitor at any endpoint, choose the method, add headers such as a bearer token, and send a JSON body. Then tell UptimePush which JSON path must equal which value, for example $.status equals "ok" or $.queue.depth below 100.

  • GET, POST, PUT, PATCH, DELETE and HEAD
  • Custom headers and request bodies
  • JSON path assertions with equals, contains, greater and less than
  • Response-time thresholds
  • Keyword presence or absence in the raw body

Catch slowdowns before users do

Set a threshold such as 800 ms and get alerted when p95 latency creeps over it. Response-time graphs show you when the slowdown started, which usually points at the deploy that caused it.

Heartbeats for the jobs behind the API

Queue workers and cron jobs do not have a URL to check. Give them a heartbeat monitor: the job pings a unique URL when it finishes, and you are alerted when the ping does not arrive on time.

Frequently asked questions

Can I monitor authenticated endpoints?+

Yes. Add an Authorization header or basic auth. Secrets are stored encrypted and never shown on status pages.

Does it work with GraphQL?+

Yes. Send a POST body with your query and assert on the JSON result.

Which plan do I need?+

JSON assertions, custom headers and POST bodies are part of Pro. Simple status-code checks are free.

Monitor your API

Start free, add JSON assertions with Pro from €9/month.

Start free – no card ↗