FiveM SDK — installation
Prerequisites
Section titled “Prerequisites”- A Spawnbase account and API tokens (Media and/or Logs) from the dashboard.
screenshot-basic— required fortakeImage/takeServerImage.
Install
Section titled “Install”- Put the
spawnbasefolder directly inresources/— not inside a category folder. - Put
screenshot-basicinresources/the same way. - Add the keys to
server.cfgas convars (never inside resource files):
set SPAWNBASE_MEDIA_API_KEY "YOUR_MEDIA_TOKEN"set SPAWNBASE_LOGS_API_KEY "YOUR_LOGS_TOKEN"Only the key for the features you use is required. The API URL defaults to
https://api.spawnbase.gg/api/v1 — no URL line needed.
- Start order in
server.cfg—screenshot-basicbeforespawnbase:
ensure screenshot-basicensure spawnbase- Restart the server (or run
ensure spawnbasein the console).
Verify it worked
Section titled “Verify it worked”From any server-side script (or a test resource), send a test entry:
exports.spawnbase:Info("default", "SDK install check", {})It appears in the dashboard under Logs → default within a few seconds
(logs flush every 5s, at 500 entries, or at 512 KB). Nothing there? Check the server
console for [spawnbase] lines — a dropped batch with a 401 means the
logs token is wrong or missing.
Migrating from the Fivemanage SDK?
Section titled “Migrating from the Fivemanage SDK?”Keep your scripts untouched: also install the fmsdk shim folder and add
one line after spawnbase —
ensure spawnbaseensure fmsdk— and your old fmsdk/config.json copies straight over
spawnbase/config.json. Full steps: migration guide.
- Configuration — log levels, datasets, auto events.
- Images — capture and upload exports.
- Logs —
Log,Info,Warn,Error,Debug. - screenshot-basic — how capture works, troubleshooting.