🔌Install the bridge resource

The FiveUnity Secure Bridge is a small server-side resource you install on your own FiveM server. It is what turns the settings on the FiveM page into real in-game actions, and what pushes player stats and logs back to Discord.

#1. Get the resource

The resource is called fivem-api-resource and is supplied by FiveUnity; there is no download button in the dashboard, so ask FiveUnity support for the current version if you do not already have a copy.

Copy the whole folder into your server's resources directory.

#2. Generate your keys

In Discord, run /setup → FiveM Bridge → Generate Key. The bot creates both keys, saves them, and replies with a block ready to paste:

set bridge_token "your-inbound-key"
set bridge_outbound_key "your-outbound-key"
set bridge_bot_url "https://YOUR_BOT_HOST:3000"

The dashboard's Rotate keys button does the same, showing the pair once in a Copy keys now panel. Either way the keys are never shown again, so copy them straight into server.cfg.

#3. Configure server.cfg

There is no config file to edit: the bridge reads everything from convars. Put these lines in server.cfg above the ensure line:

# FiveUnity Bridge
set bridge_token "your-inbound-key"
set bridge_outbound_key "your-outbound-key"
set bridge_bot_url "https://the-address-fiveunity-gave-you"

ensure fivem-api-resource

Finally, on the dashboard FiveM page, set Server IP to your public game address (for example 203.0.113.10:30120) and turn Integration on.

#4. Framework detection

The bridge detects your framework by itself; there is nothing to configure. On start it looks for Qbox (qbx_core), QBCore (qb-core) and ESX (es_extended), retrying for about 60 seconds and again whenever one of those resources starts. Your server console prints one of:

[FiveUnity] Detected Qbox Framework
[FiveUnity] Detected QBCore Framework
[FiveUnity] Detected ESX Framework
[FiveUnity] No supported framework detected (Qbox/QBCore/ESX). Economy and medical endpoints will be limited.

Individual features look for their own resources on top of that:

Start your framework before or alongside the bridge. Nothing breaks if it starts later, but detection has to catch up.

Those links are made automatically and re-checked whenever a resource starts or stops. Your console says which one was picked:

[FiveUnity] Weather/time linked to vSync (resource "vSync-1.4.0")

#Whitelist

With Whitelist switched on for the FiveM page (and a whitelist role picked), the bridge checks every player as they connect: they need Discord linked in FiveM and the whitelist role in your Discord. Anyone else sees a short message saying what to do. Decisions are cached for a minute, so a reconnect does not hit the bot twice. If your server cannot reach the bot at that moment the player is let in and the console warns; add set bridge_whitelist_strict "1" to server.cfg if you would rather refuse joins until the bot answers.

#5. Ports and firewall

The bridge does not open a port of its own: it answers on your FiveM server's main HTTP port, normally 30120. Allow inbound TCP on that port so the hosted bot can reach it, and make sure your server can reach the internet over HTTPS for the outbound pushes.

If your server is only reachable on a private or LAN address, turn on Allow private / LAN addresses on the FiveM page. Link-local and cloud metadata addresses stay blocked regardless.

#6. Test the connection

Restart your server (or ensure the resource), then test from either side:

• Dashboard (Roleplay → FiveM → Test bridge. Success reads "Bridge reachable. Framework: QBCore. Weather/time: vSync (vSync-1.4.0). Inventory: ox_inventory.") everything after the framework is a resource the bridge linked itself to.
• Discord: /setup → FiveM Bridge → Test Bridge. Success reads "Success! Bridge Active. Framework: QBCore. Weather/time: vSync (vSync-1.4.0)."

A framework of None means the bridge answered but has not detected Qbox, QBCore or ESX yet. "Weather/time: no sync resource found" means none of the weather resources above is started, so weather and time commands use your server's own console commands.

#What the resource sends back

Once running, the bridge pushes player data on its own: 15 seconds after a player joins, when they disconnect, and for everyone online every 2 minutes. Each push carries the player's name, identifier, cash, bank, job and job grade; this is what /player-info shows as last sync.

Players are matched by their Discord identifier, so a player must have Discord running and linked when they connect for commands that target a Discord user to find them.

Your own server-side scripts can add entries to the log channels by triggering the resource's fiveunity:log* events (or calling its log* exports). All of them are server-only: game clients cannot trigger them, so players cannot forge log entries.

Two captures run without any script work: deaths are logged from baseevents:onPlayerDied / onPlayerWasted while bridge_death_events "1" (the default) is set, and with bridge_money_events "1" the bridge also logs framework money events (QBCore OnMoneyChange, ESX addAccountMoney / removeAccountMoney) and job/duty changes (QBCore OnJobUpdate / SetDuty, ESX esx:setJob) into the money and job channels. See the resource README for the full payload shapes and the rate limits (20 money/transaction/job entries and 40 death entries a minute).

#Troubleshooting

#Related

• FiveM
• In-game commands from Discord
• txAdmin