Asset API  

1. Support for the older V3 API will be provided until April 2026.
   
2. All CRUD operations are supported in the APIs. However, only old asset and workstation additional fields, along with CI attributes created before the migration, will be fetched in the old APIs.
   

For CMDB API, refer to this document. 

Add Asset 

1. The assets API is renamed to asset_assets.
   
2. The asset_assets API does not support the Add Asset operation.
   
3. Previously, a common API was used for product types. Now, there is a separate API for each product type. 
   

Get All Assets

1. For GET requests, provide the input_data in GET Params section, and encode the input_data before sending the request.
   
2. The older assets API in the released version fetches all access points as mentioned in  "filter_by": { "id": 9 }
   
3. The new asset_assets API fetches all assets, including custom product types and components.
   
4. To fetch assets under a specific product type, you can either use API specific to the product type API (e.g., api/v3/asset_access_points), or use the search_criteria field with module.id instead of product_type.id.
   
5. Using the API specific to the product type will list all the assets including the assets of child product types. Whereas using search criteria lists only the assets of that particular module.
   
6. The asset_assets API does not fetch product type-specific fields such as subforms and UDFs. Only the basic fields (fields included for the Asset product type) are returned.
   

Get Metainfo  

1. Use the API specific to the product type to get the metainfo.
   
2. Additional fields created under Admin > Customization > Additional Fields > Asset must be associated with a product type layout to appear in the metainfo.
   
3. Template ID (product type ID) is not required in the input data.
   

Workstations  

1. The workstations API has been renamed to asset_computers.
   
2. The is_server field is deprecated. Use the asset_servers API to fetch details.
   
3. Certain field names in the Processors subform have changed.
   
1. model → cpu_model
   
2. serial_number → cpu_serial_number
   
3. Processor speed field input format is now a number instead of a string.
   
4. Memory fields (both individual fields and those within subforms), such as free_space, capacity, virtual_memory, total_memory etc, now require an input in the format of a value and a unit (e.g., 8GB)
   
5. In network_adapters, the dhcp field (string) is replaced by is_dhcp (boolean). Similarly, in printer_details, the is_default field is changed from string to boolean.
   
6. Groups like sound_card and keyboard are now subforms and allow multiple entries.
   
7. All groups (e.g., memory, operating_system, computer_system, etc.) are removed. Their fields are now individual fields. For example,
   
1. operating_system.os → os_name
   
2. computer_system.service_tag → service_tag
   
8. computer_system.system_manufacturer and computer_system.model fields are removed as these are same as manufacturer and product fields.
   

Get Workstations  

Update Workstations  

Get Servers 

Get CI Attributes of Asset 

1. CI attributes are not supported in the new V3 API.
   
2. Only additional fields associated to a product type are supported for search, get, and update operation.
   
3. Existing CI attributes will be changed into additional fields and mapped to the respective product types. For example,
   
1. Attributes from the base element CI (Default Attributes) → Additional fields under the Asset product type
   
2. Attributes from Workstation CIs →Additional fields under the Workstation product type
   
3. Attributes from Server CI → Additional fields under the Server product type
   
4. Asset Additional fields  → Additional fields under Asset product type
   
5. Workstation Additional fields → Additional fields under Computer product type.
   

 Get Asset Linked to CI

1.  Not all assets are CIs, and an asset cannot be searched by using a CI ID. However, if an asset is linked to a CI, to can be searched by using the linked_instance field.
   

 Get Virtual Hosts

1. No separate API exists for virtual hosts.
   
2. Use the vm_platform field to fetch virtual hosts.
   

Get Virtual Machines

1. No separate API exists for virtual machines. 
   
2. Use the vm_host field to fetch virtual machines.  
   

 Virtual machines can be fetched only by providing the host details.

Fetch Virtual Machines Under a Virtual Host 

 Get Associated Software 

Get Workstations Based on IP Address 

Get Assets Based on IP Address  

Add Costs 

1. Add costs operation is supported in asset_assets API.
   
2. The cost factor ID can be fetched by using the API api/v3/asset_assets/{asset_id}/costs/cost_factor. 
   
3. The asset_cost key is changed to asset_sub_cost.
   

Get Disposed Assets 

 Add Attachments 

Fetch Attachments List

Download Attachments  

Convenience Operations  

1. All convenience operation keys (e.g., metainfo, copy, etc.) must be prefixed with an underscore (_) in the URL (i.e., api/v3/asset_servers/_metainfo and api/v3/asset_servers/_copy)
   
2. The API for configuring depreciation is no longer supported. Depreciation must now be configured for an asset using an update operation.
   

Bulk Update Assets  

1. The bulk update API allows you to update the fields of multiple assets with different values.
   
2. Use asset_id in the input data to update assets.
   
3. Only base fields (fields available for the Asset product type) can be updated using the asset_assets API. To update additional fields and other product type specific fields, use the corresponding product type's API.
   

Fetch Assets with Service Tag

Fetch Assets with User 

 Fetch Assets Associated to User

 Fetch Assets Based on State  

Get All Assets (Including Disposed Assets )

Fetch Assets from Requester Login   

Fetch Product Types from Requester Login