BI Assets Endpoint
Access asset data in a flattened format optimized for Business Intelligence tools. All fields are at the root level for direct column mapping.
Available Endpoints
| Method | Endpoint | Description |
|---|---|---|
| GET | /bi/v1/assets | List all assets in flattened format |
| GET | /bi/v1/assets/count | Get total count of assets |
| GET | /bi/v1/assets/{id} | Get a specific asset by ID |
List All Assets
Returns a paginated list of assets with all fields flattened to the root level. Ideal for bulk data export to BI tools.
Query Parameters
| status | Filter by asset status (e.g., ACTIVE, INACTIVE) |
| policy | Filter by assigned policy path name |
| page | Page number (0-indexed, default: 0) |
| size | Page size (default: 20, max: 100) |
| sort | Sort field and direction (e.g., lastSyncAt,desc) |
curl "https://api.nomid.tech/emm/api/bi/v1/assets?page=0&size=100" \
-H "X-API-Key: nm_acme_abc123..."Get Asset Count
Returns the total count of assets matching the filter criteria. Useful for pagination calculations.
GET /bi/v1/assets/countGet Specific Asset
Returns a single asset in flattened format by its asset ID.
GET /bi/v1/assets/{id}BiAssetDto Schema
Each asset object follows the BiAssetDto flat structure. All fields are strings at the root level - no nested objects or arrays.
| Field | Description |
|---|---|
| pathName | Full asset path (e.g., enterprises/acme/assets/abc123) |
| identification | User-friendly identifier for the asset |
| name | Device name |
| description | Device description |
| serialNumber | Device serial number |
| imeis | IMEI numbers (comma-separated if multiple) |
| brand | Device manufacturer/brand |
| model | Device model name |
| status | Asset status (ACTIVE, INACTIVE) |
| lastSyncAt | Last synchronization timestamp (ISO 8601) |
| enrollmentTime | Device enrollment timestamp (ISO 8601) |
| policyPathName | Full path of assigned policy |
| policyDisplayName | Human-readable policy name |
| policyGroupName | Policy group for categorization |
| metadata | Custom metadata as JSON string |
| tags | Tags as comma-separated string |
| operatingSystem | OS name (e.g., Android) |
| operatingSystemVersion | OS version number |
Public API vs BI API
The main difference is the response structure. Public API uses nested objects for organization, while BI API flattens everything for easy column mapping.
Pagination
Results are paginated using the same format as the Public API. Use page and size parameters to navigate through large datasets.