Find your listings
Before you can call any listing-specific endpoint, you need that listing’s ID. These endpoints let a script figure that out for itself instead of you copy-pasting IDs out of the dashboard.
You’ll need an API key. These endpoints only return what your key’s account owns or manages - there’s no way to browse other accounts’ listings by user.
Who am I?
@me is the only supported value - there’s no general user-lookup endpoint. Returns the account the key belongs to.
What do I own?
Each returns every listing the key’s account owns or co-manages, with a role field so you can tell the two apart.
role is "owner" or "developer" for bots, "owner" or "admin" for servers.
Looking up any listing
Once you have an ID, GET /api/v1/bots/{id} and GET /api/v1/servers/{id} return the same public fields shown on that listing’s page - for any approved bot or server, not just your own. Any valid key can call these; there’s no ownership check, since it’s the same information anyone visiting the listing page can already see.
{id} accepts a bot’s Fluxer bot ID, FluxerList UUID, or listing slug (servers use the Fluxer guild ID). Useful for pulling fresh listing data - vote count, member count, tags - into your own site or bot without scraping the page.