verify and receive Hover webhook events for capture requests, jobs, and models
domain: developers.hover.to · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a webhook URL through Hover's webhook registration endpoint
Handle the immediate webhook-verification-code POST that Hover sends to your URL, capturing the code from the payload
Call PUT https://hover.to/api/v2/webhooks/{webhook_verification_code}/verify with that code to activate the webhook
Once active, branch on the event attribute of each inbound POST to route job-state-changed-v2, model-state-changed, capture-request-state-changed, and other event types to the correct handler
Return a prompt 2xx response and make handling idempotent, since Hover retries failed deliveries up to 25 times over roughly 20 days with exponential backoff
Known gotchas
A newly created webhook stays inactive until the verification PUT completes — events silently never arrive if you skip that step
Terminal errors (400/404/500) from your endpoint are not retried, so a misconfigured route can permanently drop that event
job-state-changed (v1) is deprecated in favor of job-state-changed-v2 — build against v2 to avoid depending on a sunset event shape
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?