How to use the URN Resolver

The URN Resolver normalizes data from multiple vendors (Eagle Eye Networks, Brivo, etc.) into a consistent format. Enter a URN, list pattern, or class query in the search bar.

URN Format

A URN identifies a specific resource:

urn:<vendor>:<resourceType>:<id>

Part	Description	Examples
vendor	The vendor namespace	een, brivo
resourceType	The type of resource	camera, accessPoint, site, account, user
id	Unique resource identifier	10014782, 50234807

Actions

Input	Action	Description
urn:een:camera:10014782	resolve:urn	Resolve a single resource — returns all normalized documents
urn:een:camera:*	resolve:list	List all resources of a type from a vendor
urn:een:camera	resolve:list	Same as above — the :* is implied
class:device	resolve:class	List all resources of a class across all vendors

Available Vendors & Resources

Vendor	Resource Type	Class	List URN
Eagle Eye Networks	camera	device	urn:een:camera:*
Eagle Eye Networks	site	site	urn:een:site:*
Eagle Eye Networks	account	account	urn:een:account:*
Eagle Eye Networks	user	user	urn:een:user:*
Brivo	accessPoint	device	urn:brivo:accessPoint:*
Brivo	site	site	urn:brivo:site:*
Brivo	account	account	urn:brivo:account:*
Brivo	user	user	urn:brivo:user:*

Classes

Classes group resource types across vendors. Use class:<name> to query all vendors at once.

Class	Resources	Query
device	een:camera, brivo:accessPoint	class:device
site	een:site, brivo:site	class:site
account	een:account, brivo:account	class:account
user	een:user, brivo:user	class:user

Document Types

Each resolved resource returns a set of normalized documents. Device-class resources (cameras, access points) aim for a common envelope so consumers can render them identically across vendors — fields may be empty when a vendor doesn't expose them.

Document	Description	Appears on
ResourceInfo.v1	Resource identity — id, name, icon, dateCreated	every resource
CloudConnectionStatus.v1	Cloud connectivity — connected/disconnected/unknown	devices
OperationalStatus.v1	Device operational health — operational/error/disabled/unreachable/unknown/initializing	devices
Permissions.v1	Per-resource permissions — dotted grants map (e.g. resource.read) → vendorActions	every resource
SiteInfo.v1	Place metadata (inline) on a site URN; $ref on resources assigned to a site	sites; devices via $ref
GIS.v1	Geographic position — lat/lon coordinates	sites or devices with independent GPS
HardwareInfo.v1	Physical hardware — make, model, firmware, serial; physicalDevice ($ref) when the resource is logical (e.g. Brivo accessPoint → controlPanel)	devices
NetworkInfo.v1	Per-interface networking — name, MAC, IP, subnet	devices with network identity (EEN cameras)
AccountInfo.v1	Inline (id, name) on an account URN; $ref to the account URN on resources owned by it	every resource

View Modes

When viewing a single resource, toggle between:

• Debug — raw JSON per document (for developers)
• Consumer — formatted cards with labeled fields (for non-technical users)

API Endpoints

The same queries work via HTTP:

GET /api/v3.0/resolve:urn/urn:een:camera:10014782
GET /api/v3.0/resolve:list/urn:een:camera:*
GET /api/v3.0/resolve:class/device
POST /api/v3.0/resolve:describe  {"urn":"urn:een:camera:10014782"}