FAQ: General

FAQ: General

Answers to the most common general questions about PulseAPI.


How often does PulseAPI check my endpoints?

It depends on your plan and what interval you configure on each monitor. The minimum interval is 60 seconds on Free and Starter plans, 15 seconds on Professional, and 5 seconds on Team. See Check Intervals Explained.


Where do PulseAPI's checks come from geographically?

PulseAPI performs checks from its monitoring infrastructure. If you need to allowlist IP addresses in your firewall or WAF, contact support for the current IP ranges.


What's the difference between an alert rule and an incident?

An alert rule is the condition you define (e.g., "status code != 200"). An incident is the record that's created when a check fails and matches an alert rule. Think of the rule as the trigger and the incident as the result. See Key Concepts.


Can PulseAPI monitor non-HTTP endpoints (TCP ports, ping, etc.)?

No. PulseAPI currently monitors HTTP and HTTPS endpoints only. TCP port monitoring, ICMP ping, and DNS monitoring are not currently supported.


Can I monitor localhost or internal network addresses?

No. PulseAPI's checks are made from its own infrastructure over the public internet. Endpoints must be publicly accessible. If you need to monitor internal services, expose them via a secure tunnel or reverse proxy, or use an agent-based monitoring tool.


What HTTP methods does PulseAPI support?

GET, POST, PUT, PATCH, DELETE, and HEAD. See HTTP Methods Explained.


Does PulseAPI follow redirects?

Yes, PulseAPI follows HTTP redirects (3xx responses) by default and records the final response code. If you want to alert on a redirect itself (e.g., detect a 301 that shouldn't be there), set your alert rule condition to match the redirect status code.


Can I add custom headers to monitor requests?

Yes. See Adding Request Headers to a Monitor.


Can I monitor endpoints that require authentication?

Yes — via Basic auth, bearer token, or a custom API key header. See Authentication Options for Monitors.


What happens to my data if I cancel my subscription?

Your account downgrades to the Free plan. Check history beyond 7 days is deleted. Monitors, alert rules, and notification channels are preserved (some may be deactivated if they require a paid plan). See Canceling Your Subscription.


Is there a status page for PulseAPI itself?

Yes. See status.pulseapi.io for real-time and historical uptime of PulseAPI's own infrastructure.


Still have questions? Contact support.

    • Related Articles

    • FAQ: API

      Answers to common questions about the PulseAPI REST API. Is the REST API available on all plans? No. API access requires a Starter, Professional, or Team plan. The Free plan does not include API access. How do I authenticate API requests? Use a ...
    • FAQ: Billing

      Answers to common questions about PulseAPI billing and plans. Can I try PulseAPI for free? Yes. The Free plan is available with no credit card required. It includes up to 10 monitors, email notifications, and 7-day check history. See Plans and ...
    • SSL Certificate Errors and Warnings

      This article explains the SSL errors you might see in PulseAPI check history and how to resolve each one. Common SSL Errors SSL certificate expired What it means: The certificate's validity period has ended. Browsers and PulseAPI both reject expired ...
    • I Can't Invite a Team Member

      If the Invite Member button is missing, disabled, or the invitation fails, here are the most common causes and fixes. Checklist 1. Check your role Only Owners and Admins can invite team members. If your role is Member or Viewer, the invite option ...
    • Glossary of Terms

      This glossary defines the key terms used throughout PulseAPI and this Help Center. Alert Rule A condition you configure that tells PulseAPI when to create an incident and send a notification. Each rule has a condition type (status code, response ...