GET /v1/changes returns jobs that were created, changed or closed, in the order they changed, with a cursor. It takes every filter of GET /v1/jobs.
Keep a copy in sync
- Call
GET /v1/changeswithoutcursor. You get every open job that matches your filters, ascreated. - Save
next. Call again withcursor=<next>whenever you like: every 5 minutes or once a week. You never miss a change and you never need to call at a fixed time. - While
moreistrue, call again at once.
Each change also has its own
cursor, so you can go on from the middle of a page.
What it costs
- A
createdorchangedjob costs one credit, unless you already got it this month (from any endpoint, the MCP server or a webhook). closedevents are free.- Calling twice with the same cursor costs nothing the second time.
- On the free plan, a page stops before the first job past your quota, and
nextpoints there. Nothing is skipped.
410: start again without a cursor (jobs you already got this month are free).
Closed events of jobs we no longer store are not filtered: ignore ids you do not have.
Webhooks
Every paid plan can add up to 5 webhooks on the account page or withPOST /v1/webhooks (url, optional filters). From then on, we send the changes that match to your HTTPS URL every 30 minutes, in batches of up to 500, billed like GET /v1/changes. The body is a page of changes with the webhook’s id:
- Answer with any
2xxwithin 10 seconds. We do not follow redirects. - Each request is signed the Standard Webhooks way: headers
webhook-id,webhook-timestampandwebhook-signature(v1,and a base64 HMAC-SHA256 ofid.timestamp.body, keyed with the base64 part of yourwhsec_secret). Their libraries check it for you. - A failed batch is sent again later with the same
webhook-id(30 minutes, then doubling up to a day). After 8 failures in a row the webhook is turned off; add it again to start from that moment. - A batch may come twice if your answer is lost: drop a repeated
webhook-id.