Create a change-detection monitor
Creates a recurring change-detection monitor for a URL, delivering results via webhook. **Limits:** request bodies are capped at 512 KB. An oversized body returns a `400` with error code `request_too_large`.
Authorization
AuthorizationRequiredBearer <token>API key. Manage keys from the dashboard at app.bytekit.com.
In: header
Request Body
application/jsonRequiredurlRequiredstring"uri"typestring"screenshot"Value in: "screenshot" | "scrape"interval_typeRequiredstring"hourly" | "daily" | "weekly" | "cron"cron_expressionstring5-field cron expression. Required when interval_type is "cron".
change_thresholdnumber5Minimum: 0Maximum: 100notify_onstring"change"Value in: "change" | "every"webhook_urlRequiredstringWebhook endpoint URL (HTTPS only; http:// rejected with 400 invalid_url, reason scheme_unsupported)
"^https://"Format: "uri"webhook_secretstringHMAC secret used to sign webhook deliveries. Each delivery carries X-Webhook-Timestamp and X-Webhook-Signature (sha256= + the hex HMAC-SHA256 of timestamp.body). See https://bytekit.com/docs/guides/webhooks for verification code.
webhook_headersobjectMax 20 headers. Keys must match /^[A-Za-z0-9-]+$/ and not be reserved.
optionsobjectScreenshot monitor options (device, viewport, format, etc.).
scrape_optionsobjectScrape monitor options (formats, country, headers, etc.). Only for type=scrape.
metadataobjectArbitrary key-value metadata. Max 4096 bytes when JSON-serialized.
Monitor created.