Webhooks
Webhooks can be used to receive real-time notifications about events occurring on VaultCord
General guidance
If you are using a Discord webhook, you can ignore all the below instructions. For customizing message fully, set a channel here instead.
Create Webhook
Configure your first webhook to receive instant & live notifications about things happening with your account.
Signing/Validating
To verify the authenticity of a webhook request and its payload, each webhook request includes a X-VaultCord-Signature
header with a HMAC signature comprised of the JSON encoded request body and your webhook secret. Your webhook secret can be copied here.
Every request will be sent from 45.33.155.66
, so you could use this to verify it’s a legitimate request if you can’t use encryption for whatever reason.
Signature verification code samples
PHP
PHP
Node JS
Node JS
Python
Python
Events
Each webhook request will contain an event
JSON key in the request body. A list of supported events from Webhook Endpoints can be found below.
Event | Description |
---|---|
member.verified | Member Verified. |
member.pull_started | Member Pull Started. |
donation.paid | One of your members donated to you. |
market.paid | The order has been flagged as paid, this is the final state. |
market.refunded | An order has been partially refunded, because some members didn’t arrive |
market.added | A new marketplace seller has been added |
Logs
Each webhook request will create a Webhook Log. The object is created by the request that has been sent. It will contain all headers, and the request + response body. If your website blocks our request (always coming from IP 45.33.155.66
) you can find the RayID in the headers to see what Cloudflare rule our request triggered.