Request body
The URL to monitor.
Human-readable monitor name.
5-field cron expression (e.g.
"*/10 * * * *", "0 9 * * 1").Formats to capture on each tick. Same shape as the Scrape
formats array.URL that will receive the payload on every tick (POST).
Fetch-time options. See the Scrape endpoint.
Example request
Example response
config.fetchConfig appears only when you pass fetchConfig in the request — otherwise the server uses its defaults and omits the field from the response.
| Field | Description |
|---|---|
cronId | Monitor identifier — use it on all management endpoints. |
scheduleId | Internal schedule reference. |
status | "active" | "paused". |
config | Normalized copy of the request body, including defaulted fetch options. |
Common cron expressions
| Expression | Schedule |
|---|---|
*/10 * * * * | Every 10 minutes |
*/30 * * * * | Every 30 minutes |
0 */6 * * * | Every 6 hours |
0 9 * * * | Daily at 09:00 UTC |
0 9 * * 1 | Every Monday at 09:00 UTC |
0 0 1 * * | First day of every month |
Related
- List, update, pause, resume, delete, fetch activity: Manage monitors
- Service overview: Monitor