Skip to main content
A schedule runs one data endpoint with fixed input, every 60 to 10080 minutes, and compares each answer with the one before. When the answer differs, Peel sends the schedule.changed webhook with the new data. Use it to watch a price, a listing, a release page or a search.

Create a schedule

The first run starts within a minute and records the answer later runs compare against (last_outcome: "first"). Each run after that is unchanged, changed or failed. GET /v1/schedules lists your schedules with next_run_at, last_run_at, last_outcome and last_error. When Peel stops reading a site at its owner’s request, the site’s schedules pause: next_run_at is null and last_error is site_owner_blocked. Schedules made later start paused. DELETE /v1/schedules/{id} stops one. An account can have 20. Over MCP, use create_schedule, list_schedules and delete_schedule.

Hear about changes

Subscribe a webhook to schedule.changed and schedule.failed. Peel compares the whole answer, so a field that changes on every request, such as a timestamp the site prints, makes every run count as changed. Give the schedule a shape that picks only the fields you watch.

What it costs

Each run is a call to the endpoint and counts against your runs like any other call; it shows in Runs. A run that the quota refuses fails with quota_exceeded and sends schedule.failed. An hourly schedule runs 720 times a month; a daily one, 30 times.