Semantic website monitoring API

TrackPulse - Website Change Monitoring & Webhooks

TrackPulse is a Website Change Monitoring and Webhook Alert API offered as an assisted pilot. It supports safe on-demand snapshots, semantic comparison after a material change and signed condition-based alerts; automated scheduling remains under platform validation.

Create a monitor Read the docs Test on RapidAPI Request pilot

RapidAPI discovery posture

TrackPulse - Website Change Monitoring & Webhook Alert API

Website Change Monitoring and Webhook Alert API for B2B automation pilots. Run safe on-demand checks, detect meaningful content changes with semantic analysis and receive signed webhook alerts when your rule is met.

Website-MonitoringChange-DetectionWebhooksSemantic-AnalysisAutomation

Search intent: website monitoring · change detection · webhook alerts · semantic monitoring · automation

Open listing & choose a plan Request pilot

Persistent hourly monitoring

Website change detection that survives server restarts.

Each monitor is owned by the signed-in user, backed by a platform-managed hourly callback and secured with a per-monitor webhook secret. The dashboard only shows your own monitoring estate.

Authentication required

Sign in to create and manage persistent TrackPulse monitors. This is required so schedules and webhook settings are isolated to their owner.

Platform-managed cadence

The hourly task is not an in-memory timer: it runs through a persistent, authenticated callback after deployment.

Signal, not noise

Snapshots are deduplicated. Semantic analysis runs only after the extracted content has changed.

Signed delivery

Webhook secrets are encrypted at rest; every condition alert is signed with a timestamped SHA-256 signature.

Direct API access

Use a product-scoped key outside RapidAPI.

Pilot access includes on-demand checks; automated scheduling remains under platform validation. The entitlement includes 100 monitored URLs and is revoked when the associated subscription ends.

Confirm scope

Use the sales form to confirm authorization, scope and onboarding.

Generate one key

Open the authenticated API Access area and generate the product-scoped key once.

Call the endpoint

Send X-API-Key to POST /api/v1/trackpulse/monitors; usage headers report the remaining allowance.

curl --request POST \
  --url https://prodapi-gqe9kzue.manus.space/api/v1/trackpulse/monitors \
  --header 'X-API-Key: YOUR_DIRECT_KEY' \
  --header 'Content-Type: application/json'

Start assisted onboarding Read support guidance

Integration notes

RapidAPI-ready endpoint contracts.

Every endpoint documents a testable request shape or an explicit public-source requirement, plus a response example, so a developer can inspect the contract before running it in RapidAPI.

POST/api/v1/trackpulse/monitors

curl --request POST \
  --url https://YOUR_RAPIDAPI_HOST/api/v1/trackpulse/monitors \
  --header 'x-rapidapi-key: YOUR_KEY' \
  --header 'x-rapidapi-host: YOUR_RAPIDAPI_HOST' \
  --header 'Content-Type: application/json' \
  --data '{"url":"https://example.com","rule":"Alert if the main content changes materially.","webhookUrl":"https://webhook.site/your-test-endpoint"}'

200Example response

{"id":"tp_...","status":"active","taskUid":"task_...","webhookSigningSecret":"..."}

GET/api/v1/trackpulse/monitors

curl --request GET \
  --url https://YOUR_RAPIDAPI_HOST/api/v1/trackpulse/monitors \
  --header 'x-rapidapi-key: YOUR_KEY' \
  --header 'x-rapidapi-host: YOUR_RAPIDAPI_HOST'

200Example response

{"monitors":[{"id":"tp_...","status":"active","url":"https://example.com/","lastCheckedAt":"2026-07-18T00:00:00.000Z"}]}

Buyer FAQ

Commercial and integration questions.

Can I buy this outside RapidAPI?

Yes, after assisted approval. Pilot access includes on-demand checks; automated scheduling remains under platform validation.

How are limits enforced?

Direct keys are scoped to this product and the 100 monitored URLs allowance. Responses include usage headers; exhausted allowances are rejected.

What data is retained?

Retention differs by workflow and is documented in the Privacy notice. Do not send secrets, credentials, regulated data or content you are not authorized to process.

What support is included?

Self-service support covers verified integration and billing issues. Enterprise response targets, uptime or recovery commitments apply only when written in an order form.