Fluxer Bot List

Fluxer Bot List API Reference

The FBL v1 API provides bot and user endpoints for integrating your Fluxer bot listing with FBL. Every response is JSON. Every request that accepts a body expects `Content-Type: application/json`.

i

The v1 API is the current, supported version of the FBL REST API. There is no legacy v0 surface — all integrations should target v1.

Base URL

All v1 API requests are made to the following base URL:

https://fbl.gg/api/v1

During local development the same routes live under http://localhost:3000/api/v1/....

Authentication

Authenticate every authed request by passing your FBL API token directly in the Authorization header. You can find your token on your bot's edit page under the API tab.

Authorization: your-fbl-token-here

For example:

curl https://fbl.gg/api/v1/bots/:botid/votes \
  -H "Authorization: your-fbl-token-here"
i

Do not include a Bearer prefix. FBL tokens are passed as a raw string.

Public endpoints (like GET /bots) do not require a token and are rate-limited by IP instead.

Error shape

Every non-2xx response (except 429) uses the same envelope:

{ "error": { "code": "unauthorized", "message": "Invalid API token" } }

code is stable — safe to branch on. message is human-readable and may change between releases.

List response envelope

List endpoints use pagination via limit + offset and return:

{
  "results": [ /* … */ ],
  "limit": 24,
  "offset": 0,
  "count": 24,
  "total": 8317
}
results object[] required

Array of objects for this page. Shape depends on the endpoint.

limit number required

The limit value used for this request.

offset number required

The offset value used for this request.

count number required

Number of results returned in this response (≤ limit).

total number required

Total number of rows matching the query across all pages.

Rate limits

All v1 endpoints are rate-limited. Bot endpoints have stricter limits than other endpoints and are capped at 60 requests per minute. Exceeding the limit returns 429 Too Many Requests. Include appropriate backoff and retry logic in your integration.

See Rate Limits for headers, the 429 body shape, and Retry-After semantics.

Next

Next

Bots