White Papers

APIs
14 Updating Firmware using OpenManage Enterprise APIs
Attribute Name Type Description Required
CatalogId Integer ID of the catalog—Users must enumerate all catalogs
and match the “Name” of the repository with the input
provided while creating the catalog
Yes
RepositoryId Integer ID of the repository – Derived from the catalog response Yes
DowngradeEnabled Boolean Indicates if the firmware can be downgraded No
Is64Bit Boolean This must always be set to true—The size of the DUP
files used is 64-bits.
No
Targets: Array The DeviceID, if the baseline is being created for
devices or, the GroupID, if the baseline is being created
for a group of devices.
DeviceIDs can be determined through
/api/DeviceService/Devices
Yes
Id Integer GroupIDs can be determined through
/api/GroupService/Groups
Type:
Id String ID for the device type – DeviceType IDs can be
determined through /API/DeviceService/DeviceType
Name String Type of the target (DEVICE or GROUP) Yes
Example: Request Payload
{
"Name":"adpbaselinetest1",
"Is64Bit":true,
"Description":"",
"CatalogId":104,
"RepositoryId":94,
"DowngradeEnabled":true,
"Targets":[
{
"Id":40374,
"Type":
{"Id":0,"Name":"DEVICE"}
}
]
}
HTTP status: 201 (Indicates successful baseline creation)
Example: Response Payload
{
"Id": 0,
"Name": "adpbaselinetest1",
"Description": "",
"LastRun": null,