Choose appropriate schedules
Match schedule frequency to your data needs and budget. Each scheduled run creates a billable job.Schedule formats
Define schedules in natural language with explicit timezone.- Daily schedules
- Weekly schedules
- Multi-day intervals
- sub-24h (if your plan allows it)
"every day at 12 PM UTC""every day at 9 AM EST"
Testing procedure
Test your schedule format before production use.1
Create test monitor
Create a monitor with your desired schedule (e.g.,
"every day at 3 PM UTC")2
Wait for execution
Wait for the scheduled time to pass.
3
Verify cron expression
Check the
cron_expression field:4
Create production monitor
If correct, create your production monitor. If incorrect, adjust the schedule format.
Implement robust webhooks
Configure webhook endpoints to handle notifications reliably.Endpoint requirements
Your webhook endpoint must:- Return 2xx status code within 5 seconds.
- Be publicly accessible (not localhost or private network).
- Use HTTPS (not HTTP).
- Handle POST requests with JSON body.
Quick implementation
Return 200 immediately and process asynchronously to avoid timeouts:- Python
- TypeScript
- Java
Update monitor configuration
Update webhook assignments or the record limit for an existing monitor without recreating it.When to update
Update a monitor when you need to:- Change which webhooks receive notifications
- Clear all webhook assignments
- Adjust the maximum records per run
Schedule and reference job cannot be modified. To change the query or schedule,
create a new monitor.
Update procedure
1
Get the webhook ID
If you don’t have the webhook ID, list your webhooks:
2
Send update request
"webhook_ids": [].3
Verify update
List your monitors to confirm the change took effect:

