Create Identifier
Create a new identifier for an account.
POST https://api.sonorancad.com/v2/emergency/accounts/{accountUuid}/identifiers
Rate limit:
10 requests per minuteAuthenticated v2 endpoints are rate limited per API key rather than per IP address.
Create a new identifier for an account.
Path Parameters
accountUuid
string (uuid)
Sonoran CAD account UUID.
Request Body
All identifier properties are optional in the backend. If omitted, the server uses the defaults shown below.
status
integer
No
0
Initial identifier status. See UNIT_STATUS below.
aop
string
No
""
Optional area of patrol string.
unitNum
string
No
"NEW UNIT"
Displayed unit number.
name
string
No
"NO NAME"
Identifier display name.
district
string
No
"NOT SET"
District name.
department
string
No
"NOT SET"
Department name.
subdivision
string
No
"NOT SET"
Subdivision name.
rank
string
No
"NOT SET"
Rank label.
group
string
No
""
Optional persistent group name.
page
integer
No
-1
CAD page enum. See UNIT_PAGE below.
isDispatch
boolean
No
false
Marks the identifier as a dispatcher.
Example Request
Use this tab only when calling the v2 API from the server side of an in-game FiveM resource.
Sonoran.lua and Sonoran.js: use the
sonorancadexport to get the ready CAD client.Sonoran.Net: FiveM exports do not return a .NET client. Read the Sonoran CAD convars and create a fresh client.
Sonoran.py: FiveM does not run Python resources; use the Python tab for external integrations.
The API key is stored in sonoran_apiKey as a protected FiveM convar. FiveM restricts a convar after add_convar_permission is configured, so only explicitly permitted resources can read it. Grant another resource access with add_convar_permission your-resource-name read sonoran_apiKey. If you change the API key in config.json, fully restart the sonorancad resource before reading the updated convar value.
Sonoran.lua
Sonoran.js
Sonoran.Net
After getting the Lua export client:
Import this YAML into Postman with Import -> Raw text to create a single-endpoint request collection for this route.
Response
Successful requests return application/json.
Enumeration Values
UNIT_STATUS
0
UNAVAILABLE
1
BUSY
2
AVAILABLE
3
ENROUTE
4
ON_SCENE
100
OFFLINE
UNIT_PAGE
0
POLICE
1
FIRE
2
EMS
3
DISPATCH
-1
UNKNOWN
Last updated
Was this helpful?

