Discord alt detection API

The API is REST, returns JSON and authenticates with a bearer token. Three endpoints cover what a moderation integration needs:

• GET /v1/users/<id> — the identity card: username, avatar, account creation date, public flags.
• GET /v1/users/<id>/alts — the three confidence layers of linked accounts (certain, medium, possible) with VPN attempts, server verifications and the latest fingerprint.
• POST /v1/users/lookup — identity cards for a batch of IDs in one call, returned in the order you sent them.

Call them from your own backend, never from a browser: the token must stay on your servers. In a bulk lookup, opted-out users come back flagged as opted out, never with their data, and deleted accounts come back empty. The full reference, with request and response examples, lives in the developer portal.

Create keys from the developer portal. A token is shown once, at creation: store it in your secrets manager, and revoke it and mint a new one if it leaks.

Each key has a mode. Live keys hit production data and are metered. Test keys return deterministic fixture data from the same endpoints, never bill, and never touch your usage — use them in CI and local development.

Set an IP allowlist on every production key, so a leaked token is useless outside your own servers. Every key also carries its own rate limit, visible in the portal in real time. Revoke the keys you no longer use: one key per service keeps a leak contained. Test and live keys share the same endpoints, so switching is a change of token, not of code.

The API is metered per request, graduated by volume: no included quota, no minimum, and the unit price drops as your monthly volume grows. A bulk lookup is billed per ID, in a single HTTP call.

API billing is separate from the web plans: calls are metered on their own invoice, whatever plan you have on doogle.gg. Current rates are in the developer portal, next to your usage for the month.

Test mode is where to start: the same endpoints and rate limits, fixture data, no invoice. Once you go live, your month-to-date usage and estimated cost are in the portal, and a call to /v1/me returns them for the key you are using — without billing it or counting it against the rate limit.

• Verification bots that check every new member on join and flag the ones with certain alts before they post.
• Moderation dashboards for large communities, where the mod on shift sees linked accounts next to the report queue.
• Raid clean-up: after a raid, a bulk lookup over every account that joined, then the alt report on the ones that matter.

The data is the same the web report shows, so the rules are the same too: use it to protect your community, never to dox anyone. Moderators who only need a few searches a day will find the web plans simpler. Whatever you build, cache identity lookups: profiles change rarely, and every live call is billed. Start with test keys and a handful of IDs you already know.