Skip to main content
Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. If you like what you see, join us in person at the ninth annual Jamf Nation User Conference (JNUC) this October for three days of learning, laughter and IT love.

Every aspect of the Jamf web GUI should be accessible via the API

For every option that is configurable via the Jamf Pro web GUI, we should also be able to set that via the Jamf API.

A simple example would be in Policies accessible in Self Service. In the GUI we are able to set the Button name for a Self Service Policy before installation and after installation. Via the API, you can only set the Button text for before the Policy is installed

Comment
Order by:

Posted: by grahamrpugh

+1.

And please don't mark this duplicate with specific requests for specific GUI actions such as the one above.

Let's have a commitment from Jamf - no new features without an API action... and then, make all existing features API'able too.

Like

Posted: by BrandonKurtz

+1

Like

Posted: by mm2270

Agreed 1000%

Like

Posted: by Gregory

Yes, we should be able to act on anything available in the GUI!

Like

Posted: by LRZ_Jamf

Yes, and theres much more missing than this point.

Like

Posted: by bpavlov

Something like this seems relevant here as an example of data that should be available via the API:
https://www.jamf.com/jamf-nation/feature-requests/5963/make-all-building-information-available-via-api

Like

Posted: by bpavlov

Also, someone on Slack mentioned Bookmarks/Plugins in Self Service being made accessible via the API.

Like

Posted: by grahamrpugh

@bpavlov that was me :)

Like