Waymark / Routes / ghost.org register webhooks for Ghost member lifecycle events (added/edited/deleted)
domain: ghost.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps POST to /ghost/api/admin/webhooks/ with event (e.g. member.added, member.edited, member.deleted) and target_url Optionally add a name and secret for identifying/signing the webhook in your own logs Ghost sends an HTTP POST to target_url when the event fires; any 2xx response is treated as success Update the target URL or event with PUT /ghost/api/admin/webhooks/{id}/, or remove it with DELETE /ghost/api/admin/webhooks/{id}/ Pair member.deleted with your own data-retention/GDPR workflow to purge downstream copies of member data Known gotchas There is no GET/retrieve endpoint for webhooks — you can only create, update, and delete; track webhook ids yourself when you create them CSV-based member imports do not trigger member.added or member.edited webhooks, only API/UI member actions do Any non-2xx response is treated as a delivery failure and the response body is discarded, not logged for you
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