Receive real-time Roblox Open Cloud webhook notifications for events like moderation actions or user reports
domain: create.roblox.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Stand up an HTTPS endpoint that can accept POST requests and return a 2XX response within 5 seconds
Register the webhook in the experience's Open Cloud settings and select which event triggers should be sent to it, up to 5 webhooks total
Set a webhook secret so Roblox includes a roblox-signature header on each notification, and verify that signature before trusting the payload
Process the notification payload and acknowledge quickly; do heavier processing asynchronously after responding
Monitor for delivery failures — Roblox retries a failed notification using a fixed window before giving up on that notification
Known gotchas
If your endpoint doesn't respond within 5 seconds or doesn't return a 2XX status, Roblox treats it as a failed delivery and enters its retry sequence rather than waiting indefinitely
After repeated failed retry attempts, Roblox stops trying to deliver that notification entirely — there's no manual replay, so a prolonged outage on your endpoint means silently lost events
roblox-signature verification is opt-in (only sent if you configured a secret) — an endpoint that skips secret configuration has no built-in way to confirm a notification actually came from Roblox
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?