White Papers

APIs
14 Updating Firmware using OpenManage Enterprise APIs
Attribute Name T
y
pe 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 creatin
g
the catalo
g
Yes
Repositor
y
Id Inte
g
er ID of the repositor
y
–
Derived from the catalo
g
response Yes
Down
g
radeEnabled Boolean Indicates if the firmware can be down
g
raded 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
T
y
pe:
Id String ID for the device type – DeviceType IDs can be
determined throu
g
h /
A
PI/DeviceService/DeviceT
y
pe
Name Strin
g
T
y
pe of the tar
g
et
(
DEVICE or GROUP
)
Yes
Example: Request Payload
{
"Name":"Dell Online - Individual Devices",
"Description":"",
"CatalogId":24,
"RepositoryId":14,
"Targets":[
{
"Id":25004,
"Type":{
"Id":0,
"Name":"DEVICE"
}
}
]
}
HTTP status: 201 (Indicates successful baseline creation)
Example: Response Payload
{
"Id": 0,
"Name": "Dell Online - Individual Devices",
"Description": "",
"LastRun": null,