Bash

These are provided only as basic examples to build upon when crafting a solution that best fits your environment and needs.

By no means is anything here to be taken as a best practice suggestion.

API access should be highly restricted, if allowed at all.

If you're going to use the Jamf API, it is important to take steps to be as secure as possible.

I would suggest looking at the API authentication options presented at the link below, by user macnotes rather then the methods given in any of these examples.

https://github.com/macnotes/jamfscripts/tree/main/jamfpro/getJamfApiCredentials

Always test before using, never test in prod, use these at your own risk.

Name		Name	Last commit message	Last commit date
parent directory ..
Adobe		Adobe
Apple		Apple
Crowdstrike		Crowdstrike
DEPNotify		DEPNotify
Fiery		Fiery
Jamf		Jamf
Nudge		Nudge
Palo Alto		Palo Alto
SMB Shares		SMB Shares
Snippits		Snippits
VMware		VMware
z_Depreciated		z_Depreciated
z_To Rework		z_To Rework
ReadMe.md		ReadMe.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ReadMe.md

These are provided only as basic examples to build upon when crafting a solution that best fits your environment and needs.

API access should be highly restricted, if allowed at all.

If you're going to use the Jamf API, it is important to take steps to be as secure as possible.

Always test before using, never test in prod, use these at your own risk.

FilesExpand file tree

Bash

Directory actions

More options

Directory actions

More options

Latest commit

History

Bash

Folders and files

parent directory

ReadMe.md

These are provided only as basic examples to build upon when crafting a solution that best fits your environment and needs.

API access should be highly restricted, if allowed at all.

If you're going to use the Jamf API, it is important to take steps to be as secure as possible.

Always test before using, never test in prod, use these at your own risk.