Platform-managed cadence
The hourly task is not an in-memory timer: it runs through a persistent, authenticated callback after deployment.
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.
Use this site to verify the contract and demo. Select a plan and receive marketplace credentials through RapidAPI.
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.
Search intent: website monitoring · change detection · webhook alerts · semantic monitoring · automation
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.
Sign in to create and manage persistent TrackPulse monitors. This is required so schedules and webhook settings are isolated to their owner.
The hourly task is not an in-memory timer: it runs through a persistent, authenticated callback after deployment.
Snapshots are deduplicated. Semantic analysis runs only after the extracted content has changed.
Webhook secrets are encrypted at rest; every condition alert is signed with a timestamped SHA-256 signature.
Foundry/API provides the product explanation, demo boundaries and contract reference. The public RapidAPI listing is the single commercial path for plan selection, billing and marketplace credentials.
Review the request shape, limits and a bounded demo using only authorized inputs.
Open the listing and select the plan that matches your expected usage. 50 monitor operations/month
Use the RapidAPI snippets and marketplace credentials shown on the listing; do not expose credentials in source code or templates.
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 through RapidAPI.
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"}'{"id":"tp_...","status":"active","taskUid":"task_...","webhookSigningSecret":"..."}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'
{"monitors":[{"id":"tp_...","status":"active","url":"https://example.com/","lastCheckedAt":"2026-07-18T00:00:00.000Z"}]}Choose a plan on the linked RapidAPI listing. The marketplace manages billing and provides the credentials and request snippets for the gateway.
50 monitor operations/month The listing shows the applicable plan and the request contract documents product-level safeguards.
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.
This site explains verified integration boundaries and support guidance. Marketplace plan questions and billing are handled through RapidAPI.