API overview

The FluxerList API gives server and bot owners programmatic access to their own listings. All endpoints return JSON.

https://fluxerlist.com/api/v1

Authentication

Every request needs an API key, sent as a bearer token. Keys start with fl_.

Authorization: Bearer fl_your_api_key_here

A key belongs to one account. Lookup endpoints (getting a bot, a server, or /users/@me) work for any valid key. Everything else only works on listings that account owns - or, for bot stats and vote checks, on bots where it’s a listed developer. Widget badges don’t need a key at all.

Any FluxerList account can generate its own key from the Dashboard’s Developer tab - no request or approval needed. See API quickstart.

Pagination

List endpoints use page and limit query parameters, and return total, page, and limit alongside the results.

Errors

Errors return an appropriate HTTP status and a JSON body with an error message.

{ "error": "Forbidden" }

Rate limits

Keys can be rate limited. When one is, the response is 429 with a Retry-After header in seconds, and a body that includes remaining and reset, the time until the limit resets in milliseconds. Wait for Retry-After before retrying, and cache responses where you can.

Guides