StatusPulse StatusPulse
← All features

Developer · Free+

Public read API + tokens

The same data the public HTML page shows, in JSON. Build internal dashboards or chatbot integrations without scraping HTML or paying us per-request.

Why you need it

Read API tokens at /Dashboard/API tokens; the token's tenant plan dictates the rate limit pool so paid tiers visibly outperform anonymous IP-bucket quotas.

  • Four endpoints, no auth required for read. /api/v1/status (overall + per-monitor state), /api/v1/incidents (active + 30-day history), /api/v1/probes (probe metadata + latest result). Anonymous gets 30 req/min/IP.
  • Audit log requires a token. /api/v1/audit-log is tenant-scoped to the token's owner; cursor-paginated; filter by date / actor / entity / action.
  • shields.io-friendly badge JSON. /badge.json implements the shields.io endpoint schema so you can plug it into their renderer if you'd rather.
  • SHA-256 token storage. Raw secret shown once at creation; we keep only the hash. Last-used timestamp updates debounced to 60 s so hot tokens don't write the same row per request.

Where it pays off

Anywhere you're tempted to scrape the HTML or proxy data:

  • Internal dashboards. Pull status into Grafana / Datadog / your custom ops dashboard.
  • Status aggregators. Build "status of our entire stack" pages across all your vendors.
  • Chatbot integrations. A Slack bot that answers "are payments down?" via the API.
  • CI pre-flight checks. Block a deploy if dependencies are in active incident.

Available on Free+. Already on StatusPulse? See the full config in Help →

Related

Try Public read API + tokens in StatusPulse

5 probes, 1 status page, forever. No credit card. US or EU host — you choose.

Start free See pricing