Refreshes, schedules, and webhooks

Keep endpoint data current with durable refreshes, scheduled jobs, or an authenticated trigger.

Manual and scheduled refreshes

Publishing and manual refreshes are visible under Endpoints → Refreshes. Owners and admins can create schedules from Configuration → Schedules and choose intervals from 5 minutes through daily. A schedule can be paused, resumed, edited, or deleted. Refresh status and failure details remain in the refresh log.

Refreshes run as durable backend workflows. The serving pointer changes only after the new artifact is verified, so a failed refresh leaves the previous successful snapshot available within its freshness policy.

Authenticated refresh webhook

Use the endpoint detail Webhook tab to copy the exact URL. The general shape is:

POST https://api.qry.thedatadavis.com/e/<workspace-slug>/<endpoint-path>:refresh
Authorization: Bearer <qry-api-key>

Example:

curl -X POST \
  "https://api.qry.thedatadavis.com/e/acme/customer-health:refresh" \
  -H "Authorization: Bearer $QRY_API_KEY"

A successful trigger returns 202 with an accepted status and refresh job ID. The caller should use the Refreshes view or API to observe completion; a queued response does not mean the warehouse work has finished.