Overview
Webhook logs give moderators a live audit trail when members verify through RestoreCord. The standard webhook log sends Discord messages to a channel webhook. Enterprise custom webhooks can also send signed event payloads to your own endpoint.
- Webhook type
- Discord webhook logs
- Destination
- A Discord channel webhook URL.
- Use it for
- Moderator notifications, verification review, and staff visibility.
- Webhook type
- Custom webhook
- Destination
- Your HTTPS endpoint.
- Use it for
- Automation, analytics ingestion, CRM sync, or external risk systems.
Discord Webhook Logs
Create a private log channel
In Discord, create or choose a channel that only trusted staff can read. Verification logs can include sensitive member details depending on your settings.
Create the Discord webhook
Open the channel settings, go to Integrations -> Webhooks, create a webhook, and copy its webhook URL.
Enable logs in RestoreCord
Open Dashboard -> Servers -> Manage -> Security. Turn on Webhook Logs and paste the Discord webhook URL.
Save and test
Save changes, then run a staff verification to confirm the channel receives a new message.
@aliceNew York NY United States
Provider: Comcast Cable (AS7922)Residential
VPN: noChrome
OS: Windows 11Use a webhook name and avatar that staff recognize, such as RestoreCord Logs, so messages are easy to identify during moderation review.
Log Options
Show Logs
The Show Logs option controls whether the webhook message includes additional verification data. Keep it enabled for moderation-heavy servers, and disable it if your staff only needs a simple success notification.
Display Account Badges
Display Account Badges adds Discord account badges to the webhook message when available. This is plan-gated separately from the base webhook setting.
IP and Location Fields
IP and location details depend on IP Logging in Security settings. If IP Logging is disabled, webhook messages should not be treated as a source of IP or location evidence.
Privacy and Access
- Put verification logs in a staff-only channel.
- Do not post logs into public channels or ticket channels visible to regular members.
- Limit who can view and edit the Discord webhook integration.
- Rotate the webhook URL if it is exposed. Discord webhook URLs are bearer secrets.
- Document what member fields your server stores, especially when IP logging or email saving is enabled.
Custom Webhook
Custom webhooks are Enterprise-only and are configured in the Security tab separately from Discord webhook logs.
Custom webhooks send RestoreCord events to an external URL. The dashboard can generate a webhook secret for verifying incoming payloads. Store that secret immediately; the UI treats it as sensitive.
https://example.com/restorecord/eventsFor payload formats and signature handling, use the Webhook Events documentation.
Expected Events
- Event context
- Successful verification
- What staff should expect
- The message identifies the member, server, time, and success status.
- Event context
- Denied verification
- What staff should expect
- The message can include why verification did not complete, such as firewall or access checks.
- Event context
- Firewall decisions
- What staff should expect
- Firewall-related events can include allow, deny, or password-used context when the firewall is active.
- Event context
- Snapshot automation
- What staff should expect
- Server-level custom webhooks can also receive snapshot events when configured by the product.