Webhook Logs
Send RestoreCord verification logs to a Discord channel with a webhook, choose what each log shows, and on Enterprise post signed events to your endpoint.
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 | Destination | Use it for |
|---|---|---|
| Discord webhook logs | A Discord channel webhook URL. | Moderator notifications, verification review, and staff visibility. |
| Custom webhook | Your HTTPS endpoint. | Moderation and automation tools you operate. |
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 your server's Security tab. 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.
Discord log preview: a successful verification is posted by the webhook (for example RestoreCord Logs, shown with a BOT tag) with the message "@alice (@alice) verified in Main Community" and a green embed titled Successfully Verified, authored by the member (@alice). The embed contains these fields:
| Field | Example value |
|---|---|
| 👤 User: | 111111111111111111 |
| 🌎 Client IP: | 203.0.113.10 (hidden as a spoiler) |
| 🕐 Account Age: | 2 years ago |
| 🇺🇸 IP Info: | Location: New York NY United States, Provider: Example ISP (AS64500) |
| 🌐 Connection Info: | Type: Residential, VPN: no |
| 💻 Device Info: | Browser: Chrome, OS: Windows 11 |
Use 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
Premium. Display Account Badges adds Discord account badges to the webhook message when available.
IP and Location Fields
IP and location details depend on IP Logging in Security settings. With IP Logging off, don't rely on webhook messages for IP or location.
When there is no IP to show, the Client IP field says why:
- Upgrade to view: the server owner's plan doesn't include IP logging.
- IP Logging off: the plan includes it, but IP Logging is turned off for this server.
- Unavailable: IP Logging is on, but no IP was received for this request.
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. Copy the secret now; it's shown once.
https://example.com/restorecord/eventsFor payload formats and signature handling, use the Webhook Events documentation.
Expected Events
| Event context | What staff should expect |
|---|---|
| Successful verification | The message identifies the member, server, time, and success status. |
| Denied verification | The message can include why verification did not complete, such as firewall or access checks. |
| Firewall decisions | Firewall-related events can include allow, deny, or password-used context when the firewall is active. |
| Snapshots | Custom webhooks receive a snapshot.create event when a snapshot is created from the dashboard or API. Automated snapshots don't send one. |