Changelog

Beta 0.3.12 · Build 26

The API is public

Any FluxerList account can now generate an API key from the Dashboard’s Developer tab - no request, no ticket, no approval needed.

New endpoints

Four new groups of endpoints join the existing voter lists:

• Look up a listing. GET /bots/{id} and GET /servers/{id} return the same public fields shown on a listing page - name, avatar, invite, counts, tags, and more - for any approved bot or server.
• Check a vote. GET /bots/{id}/check and GET /servers/{id}/check return whether a specific Fluxer user currently has an active vote, without paging through the full voter list.
• Stat badges. Embeddable SVG widgets for a bot’s server/vote count or a server’s member/vote count. Public and unauthenticated, so they work straight in a README <img> tag.
• Your account. /users/@me, /@me/bots, and /@me/servers let a key identify itself and list what it owns or manages, instead of hardcoding IDs.

Bot developers, not just owners, now have full access to every bot endpoint, and we ironed out a few rough edges in voter list pagination based on early testing.

Rate limits reworked

The default rate limit dropped from 30 to 20 requests/minute, and every key now also has a 3,000/month cap shared across all its endpoints, so one key can’t exhaust the platform’s overall quota. Your Dashboard’s Developer tab shows live usage per bucket, with a progress bar and a countdown to when each one resets.

Also fixed and polished

• Fixed instance review pages not showing an uploaded icon or banner, always falling back to a plain letter avatar even when the operator had uploaded images.
• The instance review page now shows which FluxerList account actually submitted the listing, instead of only the free-text Operator Contact field.
• FLAT moved out of the navbar and into the footer’s Platform links, and a new Docs link was added to the navbar.
• Reworked the footer: Legal links moved into the bottom bar, and Platform/Community were rebalanced into two columns instead of one heavy one.
• Fixed an edge case where an account with a very large Fluxer ID could display incorrectly in a few places.
• Fixed a crash on the Dashboard (“Rendered fewer hooks than expected”) that could happen when your session expired while it was still open.