API Changelog
Stay up to date with upcoming API changes, deprecations, and new features. Entries marked as action required need your attention before their target date.
Rate limiting enforcement beginning 16th March
Guild-level request budgets and per-query/mutation rate limits have now been fully documented and will be enforced starting the week commencing 16th March 2026. All developers should review the Rate Limiting documentation and ensure their scripts, bots, and integrations are correctly configured to handle HTTP 429 responses and respect the documented limits before this date.
Raised rate limits on partnerGetMatchIds and partnerGetMatchData
The rate limits on partnerGetMatchIds and partnerGetMatchData have been raised from 10 requests per 60 seconds to 120 requests per 60 seconds per partner (an average of 2 requests per second). Partners can now process the full list of 50 match IDs in a fraction of the previous time. Limits continue to be enforced per partnerId via Redis using a fixed 60-second window.
Bifrost Discord Map Vote Bot
The official Bifrost Discord Map Vote bot is now available. Invite it to your Discord server, connect your API credentials, and let your community vote on the next map directly in Discord. The bot monitors your game servers, automatically triggers votes when score or time thresholds are met, and sets the winning map via the API. Supports multiple servers per guild with independent vote channels and trigger settings. See the Discord Bot page for setup instructions.
New field: pendingNextMap on guildGetGameState
The guildGetGameState query now returns a pendingNextMap field. When a next map has already been set for the current match (e.g. by a Discord vote), this field contains the map RCON name. Returns null if no map is pending. This is an additive, non-breaking change — existing integrations are unaffected.
New endpoint: guildSetNextMap (Discord votemap)
New mutation for Discord bot votemap integration. Run map votes in your Discord server, then call guildSetNextMap with the winning map. The map is set as the next to play and the original rotation is automatically restored afterward. Requires votemap to be enabled with mode set to "Discord via API" in the control panel.
