HTTP check quickstart

By the end of this guide you’ll have an HTTP check running, with a notification that fires when it fails. The examples monitor https://mock.codes/200, which always returns 200 OK; use your own URL if you prefer.

Create the check

Dashboard

1. Go to Observe → Monitors, open Add monitor and choose HTTP monitor.

2. Fill in the basics.

   • Name: Mock 200 endpoint
   • URL or IP: https://mock.codes/200
   • Check Interval: 5m
   • Method: GET (under Request)

3. Leave the Default notification group selected under Alerting.

4. Click Create monitor.

The check runs immediately, and the first result lands within seconds.

API

1. Create a Full access API key under Settings → API keys and export it:

   export SITEQWALITY_API_KEY="<your API key>"

2. POST to /http/job.

   curl -X POST https://api.siteqwality.com/http/job \
     -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "friendly_name": "Mock 200 endpoint",
       "method": "GET",
       "uri": "https://mock.codes/200",
       "timeout_ms": 15000,
       "run_interval_seconds": 300
     }'

3. Save the id from the response. You’ll use it to fetch results, update settings, or delete the check later.

4. (Optional) Choose notification groups.

   With group_notification_ids omitted, the monitor is attached to your account’s default group. To use other groups, pass their UUIDs at create time or later with PUT /http/job/{job_id}. An explicit [] creates a monitor that notifies no one.

The full request schema is in the API Reference.

Verify it’s working

1. Wait for the first result, then look at it.

   • Dashboard: open the monitor’s Recent Checks tab.
   • API: GET /http/job/{job_id}/recent.

2. Force a failure to test notifications. Edit the check and change the URL to https://mock.codes/500. The next check fails, and the Default group waits 3 minutes, then emails you if the monitor is still down.

3. Flip it back once the down email arrives. Restore the URL to https://mock.codes/200. The all-clear email follows after 2 healthy checks in a row.

If the email never arrives, check your spam folder and the group’s email channel. No incident opens in this flow: monitor alerts go to notification groups, and an incident opens only when the monitor is linked to a service that creates them.

What’s next

Settings reference Every field on an HTTP check, explained.

Notifications & escalation Route alerts to the right person at the right time.

Status pages Publish your check's status to customers.