IC2 API additions

Product Discussion Feature Requests
,
1

We have a few settings we’d like to see made accessible through APIs.

  • Firmware policy options including Org, group, and device levels, scheduling and disabling.
  • More options for cloning groups when creating them including firmware policy, notifications, Device System Management and LAN settings.
  • The ability to push a device level SSID configuration
2 Likes
2

duplicating orgs as well, or having a template of an organization to create an org from.

1 Like
3

  • Firmware policy: we can open two group-level API endpoints.

    1. The first endpoint will return all published firmware’s URLs and their version numbers for all managed device models.
    2. The second endpoint will be for applying individual devices’ firmware. The input will be an array of device ID, target firmware URL, version number, a “disable” flag, and scheduled update time. I.e. it is not for updating the policy, but devices’ firmware profile. The reason is that it is extremely complicated to specify a poilcy. Details are skipped. But as an API client, it is not difficult to specify individual device’s firmware profile in bulk.

  • Cloning options in creating an group: we will include all 18 cloning options.

  • This is already available now. The endpoint is
    [PUT] /rest/o/{organization_id}/g/{group_id}/ssid_settings

  • We will add an API endpoint for the “create an organization from groups” feature.

The above updates will be included in 2.15.0. ETA: Q4.

4 Likes
4

Hey Michael, this is awesome, thanks!

Though, I’m curious what makes applying group firmware policy complicated?

1 Like
5

Here are simplified explanations.

  1. To set up a org or group f/w policy, the correct product ID and hardware revision relevant to your devices must be identified and specified. It will involve opening up new API endpoint and client will need to make additional API calls. With the device level call, you don’t need to specify. (But you still need to ensure the firmware URL and version correspond to the specified device.)
  2. The “follow org policy” and “follow group policy” concepts are for human’s ease of use. For API client programs, as they know what firmware every single device should be, they can make an API call with a large request body to modify individual device’s firmare and their schedules easily and flexibly.
2 Likes
6

Thanks for that explanation. That makes sense.

2 Likes