PageRadar API

List sites

Your sites, newest first. Cursor-paginated.

Response 200

{
  "data": [
    { "id": 12, "name": "Example", "domain": "example.com",
      "created_at": "2026-08-01T10:00:00+00:00", "updated_at": "2026-08-01T10:00:00+00:00" }
  ],
  "links": { "next": null }
}

Create a site

Domains are normalized before storage — scheme and www are stripped, so https://www.example.com/ and example.com are the same site. A domain you already have is refused with 422 validation_error rather than silently creating a second one; list your sites first, or treat that 422 as "already there".

Parameters

Request

curl -X POST https://pageradar.io/api/v1/sites \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"domain": "example.com", "name": "Example"}'

Response 201

{
  "data": { "id": 12, "name": "Example", "domain": "example.com",
            "created_at": "2026-09-01T09:12:00+00:00", "updated_at": "2026-09-01T09:12:00+00:00" }
}

Get a site

One of your sites. 404 if the id is not yours.

List a site's monitors

Create monitors

Creates one monitor per URL. The response is multi-status: each URL comes back as created, skipped (already monitored) or refused for lack of quota — a partial success is a normal outcome, not an error. 201 when anything was created, 200 when everything was a duplicate, 422 quota_exceeded when nothing fits. Monitors are created active and their first check is queued immediately.

Parameters

Request

curl -X POST https://pageradar.io/api/v1/sites/12/html-monitors \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"urls": ["https://example.com/news"], "check_frequency": "hourly",
       "freshness_check_enabled": true, "freshness_threshold_hours": 12}'

Response 201

{
  "data": {
    "created": [ { "id": 88, "type": "html_change", "url": "https://example.com/news",
                   "is_active": true, "check_frequency": "hourly",
                   "freshness": { "enabled": true, "threshold_hours": 12, "url_pattern": null,
                                  "frozen_since": null, "unchanged_checks": 0, "last_new_content_at": null },
                   "last_checked_at": null } ],
    "skipped_duplicates": [],
    "quota_exceeded": []
  },
  "meta": { "quota": { "limit": 10, "used": 4, "remaining": 6 } }
}

Get a monitor

Includes the live freshness state. This is also the endpoint you poll after triggering a check: last_checked_at advances when it completes.

Update a monitor

Send only the keys you want to change.

Editable: is_active, check_frequency, monitor_full_html, elements_to_monitor, excluded_properties, focus_keywords, custom_settings, tags, email_notifications_enabled, slack_notifications_enabled, slack_webhook_url, freshness_check_enabled, freshness_threshold_hours, freshness_url_pattern.

Not editable: url — it identifies the monitor; delete and recreate to watch another page. Unknown keys are ignored rather than rejected.

Request

curl -X PATCH https://pageradar.io/api/v1/html-monitors/88 \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"check_frequency": "daily", "freshness_threshold_hours": 48}'

List content-change alerts

Cursor-paginated, newest first. severity is one of critical, high, medium, low. Before/after values are clipped at 2000 characters, with values_truncated telling you when that happened.

Response 200

{
  "data": [
    { "id": 501, "html_monitor_id": 88, "change_type": "modified", "element_type": "title",
      "old_value": "Old title", "new_value": "New title", "values_truncated": false,
      "severity": "high", "focus_keyword_affected": null, "is_read": false,
      "detected_at": "2026-09-01T07:15:00+00:00" }
  ],
  "links": { "next": null }
}

List stuck-content alerts

Run a check now

Queues one check. There is no run id: on 202, poll GET /v1/html-monitors/{'{'}monitor{'}'} until last_checked_at advances, then read the alert lists. Polling every 15–30 seconds is plenty. Do not poll by calling this endpoint again.

Outcomes

List a site's monitors

Create monitors

Multi-status, exactly like HTML monitors: created / skipped / quota-refused per URL.

Parameters

Request

curl -X POST https://pageradar.io/api/v1/sites/12/status-monitors \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"urls": ["https://example.com/checkout"], "check_frequency": "hourly"}'

Get a monitor

current_status_code is null until the first check completes. 0 is the reserved value for a connection error — a site that could not be reached at all.

Response 200

{
  "data": { "id": 140, "type": "status_code", "site_id": 12,
            "url": "https://example.com/checkout", "is_active": true,
            "check_frequency": "hourly",
            "current_status_code": 200, "previous_status_code": 503,
            "notifications": { "slack_enabled": false, "slack_webhook_url": null, "additional_emails": null },
            "tags": null, "last_checked_at": "2026-09-01T08:00:00+00:00" }
}

Update a monitor

Editable: is_active, check_frequency, tags, slack_notifications_enabled, slack_webhook_url, additional_notification_emails.

Not editable: url. Same quota rules on activation as HTML monitors.

Request

curl -X PATCH https://pageradar.io/api/v1/status-monitors/140 \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"check_frequency": "weekly", "slack_notifications_enabled": true,
       "slack_webhook_url": "https://hooks.slack.com/services/XXX"}'

List status-change alerts

change_type classifies the transition:

Parameters

Run a check now

Same semantics as the HTML check: 202 then poll the monitor. Transient errors (timeouts, 5xx) are re-confirmed about two minutes later before being recorded, so allow roughly three minutes before concluding anything.

List a site's trackers

Create trackers

One tracker per URL, for one country. The dedup identity is the triple (site, url, country): the same link in another country is a new tracker, the same triple is skipped. Multi-status — 201 when anything was created, 200 when everything was already tracked.

Parameters

Request

curl -X POST https://pageradar.io/api/v1/sites/12/affiliate-trackers \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"urls": ["https://partner.example.com/go/abc"],
       "country_code": "ES", "name": "Bookmaker", "check_frequency_hours": 24}'

Response 201

{
  "data": {
    "created": [ { "id": 501, "type": "affiliate_redirect", "url": "https://partner.example.com/go/abc",
                   "country_code": "ES", "is_active": true, "check_frequency_hours": 24 } ],
    "skipped_duplicates": []
  },
  "meta": { "credits": { "limit": 5000, "used": 1204, "remaining": 3796,
                         "period_end": "2026-09-30T23:59:59+00:00",
                         "checks_queued": 1 } }
}

Reading meta.credits correctly: credits are spent when a check runs, not when a tracker is created — so used does not yet include the checks this call just queued. checks_queued tells you how many are about to be debited.

Get a tracker

country_code is ISO 3166-1 alpha-2 and immutable; next_check_at tells you when the scheduler will look again.

Response 200

{
  "data": { "id": 501, "type": "affiliate_redirect", "site_id": 12,
            "name": "Bookmaker ES", "url": "https://partner.example.com/go/abc",
            "country_code": "ES", "is_active": true, "check_frequency_hours": 24,
            "alert_settings": { "redirect_change": true, "final_domain_change": true,
                                "status_error": true, "timeout": true, "blocked_detected": true },
            "tags": ["sports"], "last_checked_at": "2026-09-08T06:30:00+00:00",
            "next_check_at": "2026-09-09T06:30:00+00:00" }
}

Update a tracker

Editable: is_active, name, check_frequency_hours (24 / 48 / 168), tags, alert_settings.

Not editable: initial_url and country_code. With the site they are the tracker's identity, and the stored checks were run against them — changing either would duplicate an existing tracker and orphan its history. Delete and recreate instead. alert_settings is merged, so a partial PATCH keeps the toggles it does not mention.

Request

curl -X PATCH https://pageradar.io/api/v1/affiliate-trackers/501 \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"check_frequency_hours": 168, "alert_settings": {"status_error": false}}'

List executed checks (redirect chains)

One entry per executed check, newest first, with the hop-by-hop chain as observed from the tracker's country. final_domain is the field to watch: a change there is how affiliate link hijacking shows up. final_status_code is 0 when the chain could not be completed at all.

The chain is third-party content, so it is bounded: withheld entirely when the stored chain exceeds ~64 KB, and otherwise capped at 25 hops. redirect_chain_truncated tells you when what you see is not the whole story.

Response 200

{
  "data": [
    { "id": 9001, "tracker_id": 501, "final_status_code": 200,
      "final_domain": "bookmaker.example", "total_redirects": 3,
      "total_response_time_ms": 812, "is_successful": true, "error_message": null,
      "redirect_chain": [
        { "url": "https://partner.example.com/go/abc", "status_code": 302, "host": "partner.example.com" },
        { "url": "https://track.example.net/c/1", "status_code": 302, "host": "track.example.net" },
        { "url": "https://bookmaker.example/es/", "status_code": 200, "host": "bookmaker.example" }
      ],
      "redirect_chain_truncated": false,
      "checked_at": "2026-09-08T06:30:12+00:00" }
  ],
  "links": { "next": null }
}

Run a check now

Queues one check of the redirect chain from the tracker's country. It spends one credit. There is no run id: on 202, poll GET /v1/affiliate-trackers/{'{'}tracker{'}'} until last_checked_at advances, then read /checks.

Outcomes

List a tracker's alerts

alert_type

Severity is one of critical, high, medium, low. Email is sent for critical and high only.

Who am I

The account behind the token. Useful as a connectivity and scope check.

Response 200

{ "data": { "id": 1, "name": "Sam", "email": "[email protected]" } }