Skip to main content
The BloxCord Game API lets your own server scripts talk directly to the BloxCord dashboard while your experience is running. You can change ranks, write logbook entries, award points, manage sessions, fire webhooks, and more — all from Luau. Every feature is exposed through a single BindableFunction named BloxCord, parented to game.
The first argument to :Invoke() is always the method name (a string). The remaining arguments depend on the method and are documented per method in the API Reference.

Requirements

The BloxCord object only exists when the Org-Functions API is enabled for your organization. If it is disabled in the dashboard, the object is never created and game:WaitForChild("BloxCord") will yield forever.
Before you can use any method:
1

Install the BloxCord GameLink

The BloxCord V3.0 Communications script and its BloxCordInternal package must be present in ServerScriptService.
2

Enable Org-Functions

Turn on Org-Functions API in your organization dashboard. This is the master switch for every method listed in this documentation.
3

Wait for the object

The BloxCord BindableFunction is created asynchronously at startup, so always resolve it with game:WaitForChild("BloxCord") rather than indexing game.BloxCord directly.

A first call

How it works

Most methods make a network round-trip to the BloxCord backend, so treat every call as yielding. Never call them inside tight loops or on the render step.

Next steps

Core Concepts

Learn about the actor object, return conventions, and rate limits.

API Reference

Browse every available method with parameters and return values.