Migrating from Fivemanage

Change one URL. Scripts written for Fivemanage keep working, including the older v2 endpoints most installed resources still call.

You need a BasiX API key for this. Free account, 3 GB included, no card.Get your key →

1.Create a key
Create an upload-scoped key in your client area. Upload-scoped keys work on every plan, including the free one, and cannot delete anything — which is what you want in a file that ends up in a resource folder.
2.Swap the host
BasiX answers the same paths with the same request and response shapes. Replace the base URL wherever your resource holds it, and leave everything else alone.
text
api.fivemanage.com/api/v3/file → https://upload.basix.media/api/v3/file api.fivemanage.com/api/v2/image → https://upload.basix.media/api/v2/image api.fivemanage.com/api/v2/video → https://upload.basix.media/api/v2/video api.fivemanage.com/api/v2/audio → https://upload.basix.media/api/v2/audio
3.Replace the token
Your BasiX key goes wherever the old one was. The Authorization header is accepted raw, as `Bearer`, as `Key`, or as `X-Api-Key` — whichever your resource already sends.

Worth knowing

Reads and deletes work too: `GET /api/v3/file`, `GET /api/v3/file/{id}` and `DELETE /api/v3/file/{id}`, addressable by id or by path.
Your existing files are not moved by this. New uploads land on BasiX; old links keep pointing where they pointed.
What differs: SVG is not accepted, and files never expire unless you set a retention policy on a folder.

Configuration last checked against the upstream project on 2026-09-20.

Create a free account and your API key is ready in about two minutes. 3 GB included, bandwidth never billed, no card needed.

Something not working, or a script not listed? Read the full FiveM docs or ask us — we will wire it up with you.