Moving from LonexCAD

If you built something against LonexCAD, LonexStaff or the LonexCommunity store, it can keep working on LonexOne. The documented endpoints answer at your community's LonexOne address, at the same paths, taking the same fields and giving back the same JSON.

Switching over

1. In the LonexOne panel, open Developer API and make a key. Tick what the integration needs: cad.read and cad.write for LonexCAD, staff.read and staff.write for LonexStaff, store.read for store orders.
2. Change the integration's base address from your old install to your community's LonexOne address, like https://yourcommunity.lonexone.com or your own domain. Keep the paths as they are.
3. Put the new key where the old one went. The same places still work: X-API-Key, Authorization: Bearer, X-Api-Token, an api_key field in the body, or ?api_key=.

Old keys don't carry over: LonexOne never had them, and only kept hashes of its own. Make a new key for each integration so you can turn one off without breaking the others.

What's different

The data now lives in LonexOne, so a few things work the way LonexOne does:

• Every endpoint needs a key with the right permission, apart from health.php. Some old endpoints let anything through; these don't.
• People must be in the community. Discord ids are matched to members of your community on LonexOne. Someone who hasn't signed in to your community site yet comes back as not found.
• Clocking in needs department membership. clock-in.php signs on a member of that department, using their roster callsign unless you send one. Someone on duty in one department has to clock out before clocking into another.
• Traffic stops are calls. A stop started with traffic-stop.php is a "Traffic stop" call with the officer attached; its stop_id is the call's id.
• Connection tests check your main game server through its cfx.re join link. LonexOne doesn't connect to an IP and port sent in a request.
• Licence numbers are made from the licence code and id, like DL-12, because LonexOne doesn't number licences.
• Not on LonexOne: business-owned vehicles, postal codes on civilians, and lights on the live map. They come back empty.
• Webhooks are set up in the panel instead of a settings field, and sign with the X-LonexOne-Signature header. webhook-test.php fires at your first webhook. See Webhooks.
• Store orders: order_seq is LonexOne's payment number and order_number is the Tebex transaction id.

Not carried over

Only the documented endpoints are here. Endpoints the old products used internally, the LonexCAD mobile app and Stream Deck endpoints, and the lonexcad_bridge exports aren't. For in-game features, use the LonexOne FiveM resource, which you can claim from your panel. For anything new, use the v1 API.

Endpoints that work