Multiple Ways to Build

Jamf Pro has two APIs that can be used to programmatically interface with your data. Learn more about which API is right for the tool you’re building!

Classic API

The primary resource for programmatically interacting with Jamf Pro. Despite its name, this API provides the most comprehensive coverage of Jamf Pro features and functionality.

Browse the Classic API reference

Jamf Pro API

Our forward-facing in-development resource for programmatically interacting with Jamf Pro. Additional functionality is continually being added via new endpoints.

Browse the Jamf Pro API reference

Not sure which API is right? Check out in-depth guide on the differences.

Other Tools at your Disposal

Beyond the Jamf Pro APIs are these other ways to interact with your Jamf Pro instance.

Webhooks

Receive notifications when specific events occur in your Jamf Pro instance. When an event occurs, you’ll receive an HTTP payload with data pertaining to the event.

Learn more

Application & Custom Settings

Create a streamlined user experience for customizing macOS application settings and configurations.

Learn more

Managed App Config

Jamf Pro provides full support of Apple’s Managed App Configuration protocol, enabling IT administrators to specify settings for managed apps.

Browse the Classic API reference

400Returns error codes and IDs for any packages that were unable to be deleted. Possible error codes include INVALID_ID (Package ID does not exist) and SYSTEM_EXCEPTION (A system exception occurred while attempting to delete the package).