Sign up and your first monitor

By the end of this guide you will have:

1. A SiteQwality account.
2. An HTTP check running every 10 minutes against https://mock.codes/200.
3. Confirmed an incident open and resolve cleanly, with an email landing in your inbox.

Total time: about five minutes.

1. Create an account

1. Go to app.siteqwality.com/signup.

2. Sign up with Google or email + password. Both create a fresh account in the free tier — no credit card required.

3. You’ll land on the empty dashboard. The left sidebar has every product area; the right column has the “Add your first monitor” prompt that walks you through the same flow as this guide.

Notifications are already wired up

On signup, SiteQwality automatically creates a default notification group with your admin email as the destination. New monitors are attached to it by default — so you can skip notification setup for now and your first incident will email you. To customize (add Slack, change the email, route different monitors to different groups), see Notifications.

2. Create the HTTP check

Dashboard

1. Monitors → New → HTTP check.

2. Fill in the form:

   • Friendly name: Mock 200 endpoint
   • URL: https://mock.codes/200
   • Method: GET
   • Run interval: Every 10 minutes (the free-plan minimum is 60 seconds; we use 10 minutes here so the demo doesn’t spam your inbox)
   • Leave Notification groups on its default — your account’s auto-created group is pre-selected.
   • Leave everything else as default.

3. Click Create. The check runs immediately; the first result appears within a few seconds.

API

If you’d rather start from the API, generate a key first under Settings → API keys, export it, and POST:

export SITEQWALITY_API_KEY="sq_live_..."

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": 600,
    "monitor_tls": false,
    "monitor_dns": false
  }'

You’ll get back a 201 Created with the full job object. Save the id — you’ll use it to fetch results, update the check, or delete it later.

Omitting group_notification_ids attaches the monitor to your account’s auto-created default group, so the email lands in your inbox without further setup. To target a specific group, pass its UUID in group_notification_ids (GET /notification_group/list to enumerate).

3. Confirm it’s working

1. Open the monitor’s detail page. The status badge should flip to Success within one minute.

2. Scroll down to Recent runs. You’ll see one row per check result with status code, latency, and the region it ran from.

3. Force a failure: edit the check, change the URL to https://mock.codes/500, save.

4. On the next tick the monitor flips to Failure, an incident opens, and you should receive an email within ~30 seconds.

5. Flip the URL back to /200. The monitor recovers, the incident auto-resolves, and you’ll get a recovery email.

Tip

If the email never arrives, check your spam folder and confirm the channel email matches your inbox. SiteQwality only retries failed sends a few times — the Notification channels reference covers the gotchas.

What just happened

• Your check ran on a schedule from one of our edge regions.
• The result was compared against the assertions on the monitor (status code in the success list, no body keyword search).
• A change in monitor status (success → failure) opened an incident automatically.
• The incident’s notification group was looked up, fanned out to its notification channels, and each channel rendered the alert in its own format.
• When the URL recovered, the same path ran in reverse — the incident was marked resolved and a recovery message went out.

You can wire this up much further: on-call schedules pick who gets the page, escalation policies decide what to do if no one acknowledges, and a status page can publish the incident publicly. All of that is in Incident Management.

What’s next

Concepts and glossary The mental model behind monitors, checks, incidents, on-call, and notifications.

Account and team setup Invite teammates, set up SSO, generate API keys.

HTTP checks deep dive Multi-region, custom headers, body assertions, paired TLS/DNS checks.

On-call schedules Rotate responders across timezones with overrides.