Bindings assign Discord roles from Roblox data. These endpoints let you read the configured bindings and manage them programmatically. For the concept and the dashboard UI, see Bindings.
list reads the guild from the X-Guild-ID header. The write endpoints take guild_id in the body.
Binding types
List bindings
The guild to read. Must match your key’s guild.
Each binding is enriched with the resolved Discord role name and, for group bindings, the Roblox group name.
Add a binding
The Discord role to assign.
One of group_rank, gamepass, asset, badge, account_age.
Required for group_rank. 0 to 255.
Required for group_rank. Must be at least min_rank.
discord or roblox. Required for account_age.
Required for account_age.
Optional ordering hint when bindings overlap.
The Roblox group, gamepass, asset, or badge is validated against Roblox before the binding is saved. An invalid ID returns 400.
Update a binding
Remove a binding
The id of the binding to delete.
Test a binding against a user
Check whether a specific verified member would match an existing group binding. Useful for debugging “why does this person not have the role”.
The member to test. Must be verified in the guild.
The binding to test against.
A human-readable explanation, for example “User rank 12 is below minimum 50”.
The member’s rank in the group, when applicable.
Validate a group binding config
Check a group rank configuration before saving it. This validates the group exists and the ranks are sane. It is group-rank specific.
0 to 255, and at least min_rank.