PulseAPI is an uptime and performance monitoring service that continuously checks your HTTP endpoints and alerts you the moment something goes wrong. It gives your team a single place to track endpoint health, manage incidents, and understand your service's reliability over time.
PulseAPI sends HTTP requests to your endpoints on a regular schedule — as often as every 5 seconds on the Team plan. Each request is called a check. After every check, PulseAPI records the HTTP status code, response time, and any error details.
When a check fails in a way that matches one of your alert rules, PulseAPI creates an incident and sends notifications to your configured channels (email, Slack, webhook).
Monitor (Endpoint) A URL you want PulseAPI to watch. Each monitor has a method (GET, POST, etc.), a check interval, and optional configuration like request headers, authentication, or a response assertion.
Check A single HTTP request PulseAPI makes to a monitor. Checks run automatically on your configured interval and record status, response time, and errors.
Incident A problem state created when a check fails and matches an alert rule. Incidents have a lifecycle: open → acknowledged → resolved.
Alert Rule A condition you define — for example, "response time exceeds 2000ms" or "status code is 5xx." When a check violates a rule, PulseAPI creates an incident and sends a notification.
Notification Channel A destination for alert notifications: an email address, a Slack channel, or a webhook URL.
Project A way to group related monitors. For example, a "Production" project and a "Staging" project.
Team A workspace shared by one or more users. All monitors, incidents, and alert rules belong to a team.
PulseAPI monitors HTTP/HTTPS endpoints. It does not monitor TCP ports, ping hosts directly, or run end-to-end browser flows. If your endpoint returns HTTP 200 but the page is broken, PulseAPI will not detect that unless you configure a response body assertion.
Still have questions? Contact support.