Configure Regpack webhooks to push registration-status change notifications to an external system
domain: api.regpack.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Open the Webhooks tab under your Regpack project settings
Choose the events you want to trigger a webhook (e.g., status changes, new registrations)
Provide the destination URL Regpack should POST the event payload to
Verify the receiving endpoint correctly acknowledges the webhook so Regpack doesn't treat it as failed
Use webhooks instead of polling get_user_list on a schedule to reduce API call volume
Known gotchas
Webhooks are an alternative to polling, not a guaranteed-delivery queue — build retry/reconciliation logic on your side rather than assuming every event arrives exactly once
Webhook events are configured per Regpack project, so a multi-camp/multi-project Regpack account needs webhooks set up separately for each project
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?