Discord hub

Discord Server Index API

Server ids and slugs from the public directory, 500 a page, for walks past browse depth.

GET /v1/discord/servers/index

1 credit Failed requests are free

About this endpoint

GET /v1/discord/servers/index returns ids and their aligned slugs from the public directory, 500 a page. totalIds is how many ids the snapshot held and generatedAt is when it was generated. Page with page or the previous answer's page.nextCursor.

The walk stops at 200 pages, so limitReached is true when the snapshot still has ids past the last page. This route is an index, not a server record: feed each id into the server route to read the page. Game, application and announcement ids come from their own index routes. Two calls close together can return the same generatedAt.

Discord Server Index API FAQ

Why use the index instead of browsing?

Directory browse stops at 3,000 rows, while the index lists the whole public directory. The index returns ids and slugs only, so pair it with the server route for records.

How fresh is the index?

The response carries generatedAt for the snapshot, so two calls close together can return the same generatedAt.

What does limitReached mean?

True means the walk stopped at the 200-page cap while the index still had ids. totalIds tells you how many the snapshot held in total.

How many credits does an index page cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.