Skip to main content
The inventory endpoints expose your assets across every category — cloud resources, computers, custom assets, information assets, and employees. You can read them, filter them, and update their governance metadata. The API never creates or deletes assets. Reads require Read access (all:read); writes require Write access (all:write). See Scopes.

Categories

Every asset has a categoryKey: List the categories with GET /v1/inventory/categories.

List and filter assets

GET /v1/inventory/assets returns a cursor-paginated list. Narrow it with query parameters:
Read a single asset by its opaque id with GET /v1/inventory/assets/{id}.

Update governance metadata

PATCH /v1/inventory/assets/{id} updates governance metadata on one asset — ownerId, description, classification, and tags. Device facts, names, and status are never writable.
  • description is capped at 500 characters.
  • tags accepts up to 20 entries and only existing tag keys — an unknown key returns 400 validation_failed. Tag values are read-only in v1.
  • ownerId is an employee’s opaque id.

Bulk updates

PATCH /v1/inventory/assets updates governance metadata on many assets at once (1–100 ids):
Response
Bulk updates do not support tags — set tags with the single-asset PATCH. Employee-category ids in a bulk request are rejected with 403 resource_not_writable.