Skip to main content
The Gateway API provides a REST surface for real-time state information about connected bots and gateway shards. For low-latency streaming events, use the Gateway WebSocket (not covered here). The REST endpoints are useful for polling current state.
Looking for the full API Reference? Visit api-docs.fnlb.net/gateway/ for our comprehensive interactive documentation.
Common use cases:
  • 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.
All requests must include the FNLB_BUCKET_ID query parameter using your FNLB account ID.
Example: https://gateway.fnlb.net/bots?FNLB_BUCKET_ID=62e542d92a56e7ebd885a9d2

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). Request
Response (200 OK)
array
required
An array of connected bot objects.
Each bot object contains the most relevant public state fields. Common fields are documented below.
string
required
Unique identifier for the bot.
string
required
Nickname of the bot.
string
Email address associated with the bot account (where applicable).
number
required
Numeric status code describing connection state.
Offline: 0, Booting: 1, Available: 2, Busy: 3, Disconnected: 4
string
Epic account id.
number
Number of friends currently known for the bot.
string
Short presence string that may include the custom status.
object
Party information when the bot is currently in a party. If the bot is not in a party this field may be omitted.
string
Party unique id.
string
Optional playlist or game mode id for the party.
array
List of party members with their in-party metadata.
string
required
Member account id.
string
Member display name.
string
Cosmetic outfit identifier for the member.
string
Cosmetic backpack identifier.
string
Cosmetic pickaxe/harvest tool identifier.
number
Optional timestamp (ms since epoch) when an matchmaking ban expires.
Example response (200)

GET /shards

Returns metadata about connected gateway shards (clusters). Useful for monitoring cluster capacity and which shard a bot is served from. Request
Response (200 OK)
array
required
Array of shard status objects.
Common fields returned for each shard:
string
required
Shard unique identifier.
string
required
Logical cluster id.
string
Human-friendly cluster name.
string
Bot version running on the shard.
number
Number of bots requested/allocated to this shard.
number
required
Current number of connected bots on this shard.
array
Optional array of category ids associated with the shard.
array
Optional array of bot ids the shard was started with.
boolean
If true, the shard is running an older bot version.
boolean
Whether this shard is VIP.
string
OS/platform string (e.g. “Linux”).
string
The deployment source (e.g. “SelfHosted” or an internal name).
Example response (200)

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).
Looking for the full API Reference? Visit api-docs.fnlb.net/gateway/ for our comprehensive interactive documentation.