Creating a Monitor

Creating a Monitor

This article explains how to add a new monitor (endpoint) to PulseAPI. After completing these steps, PulseAPI will begin checking the URL on your configured schedule and alert you if it goes down.

Prerequisites: You must be a team Owner, Admin, or Member to create monitors.

Step 1: Open the New Monitor Form

  1. In the left sidebar, click Monitors.
  2. Click New Monitor in the top-right corner.

Step 2: Configure the Monitor

Required Fields

Name A label that identifies this monitor in your dashboard and alerts. Use something descriptive, like "Production API — /health" or "Checkout Service".

URL The full URL PulseAPI will request. Must start with https:// or http://. Examples:

  • https://api.yourapp.com/health
  • https://yourapp.com

HTTP Method The HTTP method to use for each check. For most health-check endpoints, GET is correct. Use POST if the endpoint requires a request body. See HTTP Methods Explained for guidance.

Project Assign the monitor to a project for organization. If you haven't created projects yet, a default project is available.

Optional Fields

Check Interval How often PulseAPI checks this endpoint. Options depend on your plan:

  • Free / Starter: 60 seconds (minimum)
  • Professional: 15 seconds (minimum)
  • Team: 5 seconds (minimum)

See Check Intervals Explained.

Timeout How many seconds PulseAPI waits for a response before marking the check as failed. Default is 30 seconds. Reduce this if your endpoint should always respond quickly.

Expected Status Code The HTTP status code that counts as a successful check. Default is 200. Change this if your endpoint returns a different 2xx code (e.g., 201 or 204).

SSL Verification When enabled (the default), PulseAPI validates the endpoint's SSL certificate. Disable this only if you're monitoring an endpoint with a self-signed certificate. See SSL Certificate Monitoring.

Step 3: Save the Monitor

Click Create Monitor.

You should now see the monitor in your monitors list with a Pending status badge. Within one check interval, PulseAPI will make its first request and update the status to Up or Down.

Advanced Configuration

You can add request headers, a request body, and authentication to the monitor after creation, or in the same form by expanding the Advanced section:

Related Articles

Still have questions? Contact support.

    • Related Articles

    • Creating a Project

      This article explains how to create a new project to organize your monitors. Prerequisites: You must be a team Owner, Admin, or Member to create projects. Steps In the left sidebar, click Organization (or Projects if it appears directly). Click New ...

    • Creating an Alert Rule

      This article walks you through creating an alert rule in PulseAPI. Alert rules define when PulseAPI creates an incident and sends notifications. Prerequisites: At least one notification channel must exist before you can assign it to a rule. See ...

    • Organizing Monitors with Projects

      This article covers best practices for using projects to keep your monitor list manageable as your team scales. Best Practices for Project Organization Keep the Number of Projects Small at First Start with 2–4 projects. Having too many fine-grained ...

    • Deleting a Monitor

      Deleting a monitor permanently removes it and all of its associated data from PulseAPI. This action is irreversible. Before You Delete Consider whether pausing the monitor is a better option: Pause — stops checks temporarily; you can resume later; ...

    • Creating a New Team

      This article explains how to create an additional team in PulseAPI. Steps Click your Team Switcher (top-left corner of the sidebar, showing your current team name). Click Create New Team. Enter a Team Name. Optionally add a Description for the team. ...