Autoposting your server count

With a library you already use, or with six lines and setInterval.

The stats endpoint follows the field names every bot list uses — server_count, with a bare token in the Authorization header — so a library that already posts to several lists can add this one as configuration rather than as code.

With a poster library

blapi

const blapi = require('blapi');

blapi.handle(client, {
  'discordbotlist.lol': process.env.DBL_TOKEN,
});

Without one

Six lines, and nothing to keep updated:

discord.js

import { Client, Events } from 'discord.js';

const client = new Client({ intents: [] });

async function postCount() {
  const response = await fetch(
    `https://discordbotlist.lol/api/v1/bots/${process.env.BOT_ID}/stats`,
    {
      method: 'POST',
      headers: {
        Authorization: process.env.DBL_TOKEN,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({ server_count: client.guilds.cache.size }),
    }
  );
  if (!response.ok) console.error('DBL stats', response.status);
}

client.once(Events.ClientReady, () => {
  postCount();
  // Every 30 minutes. The limit is 60 a minute; this is not a budget to spend.
  setInterval(postCount, 30 * 60 * 1000);
});

Sharding

Post the total, not the shard’s slice. Each shard posting its own count makes the number jump around as the shards check in, and the last one to post wins. With discord.js:

const counts = await client.shard.fetchClientValues('guilds.cache.size');
const total = counts.reduce((sum, count) => sum + count, 0);

The 60-per-minute limit is high enough that a shard manager posting on behalf of every shard has room to spare.

How often

Every 15 to 30 minutes is plenty. Two things make a tighter interval pointless rather than harmful:

• Re-posting the same number is cheap on our side. The page cache is only invalidated when the value actually changes, so an unchanged post costs one write and nothing else.
• The check-in timestamp moves every time regardless. It is the honest liveness signal on your listing, and it does not need a 30-second loop to stay true.

The count is not guessed from Discord. There is no documented endpoint for another application’s guild count, so before this API existed the number was typed in by hand. Posting it is the only way your page shows a real one.