Sends a sample drop to the guild's configured drops channel, through the same path a real drop takes.
Fails with a reason rather than a silent success: 400 when the platform is switched off or has
no channel, 503 when the shard hosting the guild cannot be reached. dontPing defaults to true
server-side, so checking your formatting cannot notify the whole server by accident.
POSTs the collection rather than /drops/test: the API has catch-all routes matching any two
segments under a guild, they win or lose on filesystem order, and one of them answered the test
with "Invalid platform.". One segment is the only shape they cannot claim.
OptionaldontIgnored as of the 2026-09-19 API build. A dashboard test NEVER pings.
Sending it is harmless - the route no longer reads the query parameter - but it does nothing, so
do not build a UI control on it. The role still RENDERS in the test message: the bot sends
allowedMentions: { parse: [] }, which keeps the mention highlighted and resolves nobody, so a
test shows exactly what the real notification will look like without notifying the server.
Three of the four dashboard test routes used to ping for real, this one included. Pinging a server to preview a layout is a cost with no matching benefit.
The Discord side keeps an opt-IN: /setup test with_ping:True.
Optionalgames?: { OptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkickOptionalkick"Toggle Notification" switches - see GuildDropsData. null returns one to the default (on).
OptionalkickOptionalkickOptionaltimezone?: stringOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionaltwitchOptionalwebhook?: null | {
"Force Missing Drops": sends, now, every drop still running that this server should have and has not been sent - for a server that enabled mid-campaign and does not want to wait for the next 5-minute check, or one that thinks a drop was missed. Never re-sends one already sent. Ignores the server's delivery window ("force" means now).
400 when drops are not set up or the platform is switched off; 429 within 5 minutes of the last press for this server and platform (
error.code === 'rate_limited', count down fromerror.retryAfterSeconds); 503 while the bot is starting.data.sentis how many drops were handed to the server;data.messageis ready to show.One segment (
/missing-drops) for the reason insendTestDropNotification.