- Show which bots are currently connected.
- Display party members and presence status.
- Inspect shard / cluster health and capacity.
Base URL
All endpoints require a valid API key provided in the
Authorization header using your FNLB API token. Learn more.Endpoints
GET /bots
Returns a list of currently connected bots. This endpoint is read-only and only includes bots with an active connection to the gateway (it does not list offline bots). RequestAn array of connected bot objects.
Unique identifier for the bot.
Nickname of the bot.
Email address associated with the bot account (where applicable).
Numeric status code describing connection state.
Offline: 0, Booting: 1, Available: 2, Busy: 3, Disconnected: 4Epic account id.
Number of friends currently known for the bot.
Short presence string that may include the custom status.
Party information when the bot is currently in a party. If the bot is not in a party this field may be omitted.
Party unique id.
Optional playlist or game mode id for the party.
List of party members with their in-party metadata.
Member account id.
Member display name.
Cosmetic outfit identifier for the member.
Cosmetic backpack identifier.
Cosmetic pickaxe/harvest tool identifier.
Optional timestamp (ms since epoch) when an matchmaking ban expires.
GET /shards
Returns metadata about connected gateway shards (clusters). Useful for monitoring cluster capacity and which shard a bot is served from. RequestArray of shard status objects.
Shard unique identifier.
Logical cluster id.
Human-friendly cluster name.
Bot version running on the shard.
Number of bots requested/allocated to this shard.
Current number of connected bots on this shard.
Optional array of category ids associated with the shard.
If true, the shard is running an older bot version.
Whether this shard is VIP.
OS/platform string (e.g. “Linux”).
The deployment source (e.g. “SelfHosted” or an internal name).
Notes & Best Practices
- These REST endpoints reflect currently connected state. They are useful for polling, for real-time events prefer the gateway WebSocket.
- Keep polling intervals reasonable (10-30s).

