txBridge: connect FiveM to websites and apps
Explore txBridge use cases, signed webhooks, WordPress status widgets, scoped API access, and security limitations.
txBridge is an open-source integration for connecting a running FiveM server to WordPress or your own application. It includes a server-side Lua resource, signed event webhooks, a scoped HTTP API, a WordPress plugin, and implementation documentation.
Independent third-party project. txBridge is not developed, supported, affiliated with, or endorsed by Rockstar Games, Cfx.re, or the official txAdmin project. It is not an official txAdmin management API or a replacement for the txAdmin panel.
The repository describes version 0.1.0 as an implementation and integration-test candidate, not a production-certified service. Test it in staging before deploying it to a live community.
Ideas for what you can build
These are example applications, not a promise of built-in features. Apart from the supplied WordPress status widget, the workflows below require you to build and operate your own application code.
1. Display FiveM server status on a WordPress site
The included WordPress plugin can receive signed status snapshots and expose a limited public status projection if the site owner explicitly enables public_status. Add this shortcode to a page:
[txbridge_status server="main"]The widget shows an observed player count and a freshness-aware status. A stale snapshot means the last observation is old; it does not conclusively mean FXServer has stopped. The public widget does not expose player names, administrative data, or API secrets.
2. Send restart and moderation notifications
Subscribe to signed txBridge events in your own application and notify a private Discord channel or operations service when the running server emits a scheduled restart, a warning, or another documented event. Your custom receiver is responsible for filtering, deduplication, and how notifications are delivered.
The bridge captures 17 documented txAdmin events, plus selected FiveM and bridge observations. Sensitive player and admin fields are redacted by default, and the stream is not an authoritative copy of txAdmin's history.
3. Build a private operations dashboard
With authenticated, scope-limited API access, a trusted application can read current server status, connected-player observations, resource states, and a bounded event feed. Use these observations for a private operational overview or monitoring workflow.
Do not treat connection-local player IDs as permanent accounts. The API does not provide txAdmin's complete offline player database.
4. Add narrowly authorized server actions
For example, a staff-only tool could send an announcement or restart a specifically allowlisted resource. These native actions are disabled by default and require explicit feature flags, scopes, and additional checks. A kick through the bridge is a native FiveM action, not a txAdmin ban, warning, or historical moderation record.
Keep all credentials and write actions server-side. Never put an administrative API key in a public website or Discord bot command accessible to untrusted users.
What's provided
| Integration surface | Purpose |
|---|---|
| Server-side FiveM Lua resource | Observes documented server events and exposes bounded native reads and opt-in actions. |
| Signed HTTP webhooks | Delivers events to an authorized receiver with retries and a bounded persistent outbox. |
| Scope-limited HTTP API | Provides status, players, resources, event observations, and selected native actions behind authentication. |
| WordPress plugin | Receives and stores signed events; offers administrator-only endpoints and an opt-in public status shortcode. |
| Documentation and OpenAPI | Includes deployment, authentication, operation reference, security guidance, and tests. |
Important limits
- Not full txAdmin remote management. Internal txAdmin web routes are version-dependent and the experimental adapter is disabled by default. The bridge does not provide a supported universal txAdmin management API.
- Requires a running FXServer. It cannot start a stopped server process or observe events while its resource is offline.
- Not a complete history. Offline activity, missing events, and the entire txAdmin player/moderation database cannot be reconstructed from the bounded event feed.
- Staging required. Local Lua/PHP tests are not proof of compatibility with your production server, WordPress installation, or reverse proxy.
- Protect private data. Use HTTPS, strong independent secrets, least-privilege scopes, restricted peers, and appropriate retention policies. The experimental internal adapter may expose sensitive upstream data.
Get started
- Read the txBridge installation guide and choose outbound-only webhooks or a restricted bidirectional setup.
- Review the security boundaries and authentication requirements before exposing any service.
- Consult the WordPress guide or HTTP API reference for your integration.
- Complete the repository's testing and acceptance checklist on a staging server.
Source and issues: Livvux/txBridge on GitHub. For official txAdmin support, use the citizenfx/txAdmin repository.