#JAMF PRO CLASSIC API UPDATE#
#JAMF PRO CLASSIC API PRO#
#JAMF PRO CLASSIC API CODE#
#JAMF PRO CLASSIC API PASSWORD#
#JAMF PRO CLASSIC API DOWNLOAD#

#JAMF PRO CLASSIC API PRO#

After downloading and importing the collection, click the ellipsis next to the “Jamf Pro API Authentication” collection and select Edit. The keep-alive endpoint will respond with a new token and expiration and will invalidate the previous token.īelow you will find a link to a Postman collection that can be used to generate tokens and store them as variables for future API calls in Postman. Simply send a POST to the endpoint with the existing token in an Authorization header like you would to any other endpoint (see step 3 above).

#JAMF PRO CLASSIC API CODE#

Need a little help getting started with Bearer Tokens? We've got you covered, with an example code snippet:īy default, tokens expire after 30 minutes, but you can use a currently valid token to generate a new token with a fresh 30 minute validity period, using the /v1/auth/keep-alive endpoint.

You can use the previously generated token to make calls to any other Jamf Pro API endpoint by including it in a header using the format Authorization: Bearer TOKEN_VALUE.

You should receive a response that includes a token and an expiration date similar to the following example:.

Using basic authentication, request a Bearer Token by sending a POST to /v1/auth/token.

The workflow of requesting an initial token and using that token in API requests is outlined below: In order to perform successful requests to the Jamf Pro API you must present a valid token in the Authorization header of each request. The Jamf Pro API leverages the same User Accounts and Groups functionality of Jamf Pro as the Classic API, but uses a token-based authentication scheme. For more information on the privileges required to perform a specific API operation, see Privileges and Deprecations.

#JAMF PRO CLASSIC API UPDATE#

The Create, Read, Update and Delete privileges for an account or group within Jamf Pro correspond respectively with the POST, GET, PUT and DELETE HTTP methods. Additional data will be required either in the form of a parameter value and/or a request body.The Jamf Pro API supports Bearer Token authentication and uses the standard User Accounts and Groups functionality of Jamf Pro. Getting StartedĪfter the collection has been imported and valid values have been defined for the variables, all calls should be supported with minimal input required. For more information on authentication changes to the Classic API, see the Jamf Developer Portal. Tokens will be requested as necessary, so no interaction with authentication endpoint should be necessary. This version of the collection utilizes scripts to manage the Bearer Token, which is a new authentication method supported in version 10.35.0 and later of Jamf Pro.

Protocol, hostname and port of the Jamf Pro environment

#JAMF PRO CLASSIC API PASSWORD#

Password of the user authenticating to Jamf Pro Username to authenticate to Jamf Pro with Hostname and port of the Jamf Pro environment Follow Postman's documentation to Manage Environments. Jamf recommends using environments instead of global or collection variables simply for the ease of use and potential for defining different Jamf Pro environments or users. This collection utilizes the following variables which should be defined within one of the scopes in Postman.

#JAMF PRO CLASSIC API DOWNLOAD#

Download the JSON included in this repo and select the.

For Jamf Pro Version 10.35.0 and later: Click the button to automatically import the collection into your Postman app.

For Jamf Pro version 10.34.0 and earlier: Click the button to automatically import the collection into your Postman app.

Use the following options to import the collection into Postman:

All query parameters that have a defined list of acceptable values denote the allowed values in the description of the parameter.

computercommmands and mobiledevicecommands).

Endpoints that have conditional inputs in the form of parameters or request bodies should include multiple examples (e.g.

All GET operations include at least one example response.

Pull requests or issue submissions are encouraged to enhance or update this data.

This request body may not include all fields supported by the body of the given object, however it will include those required to successfully create the object.

All POST operations include a pre-populated request body.

The following expectations were used when designing this collection: This article describes the recommended Postman configuration and setup process to import the collection, configure variables to connect it to your Jamf Pro environment and begin testing API calls and interacting with your Jamf Pro environment via the Classic API. It provides a quick method to interact with all non-deprecated endpoints. This collection is provided to assist Jamf Pro users of the Classic API.

Jamf pro classic api