#JAMF PRO API UPDATE#
#JAMF PRO API PRO#
#JAMF PRO API CODE#

The personal data provided shall be shared by JCommerce Sp.

or sent to the following e-mail address: The withdrawal of consent to the processing of personal data shall result in the inability to fulfil the aforementioned processing purposes

A statement of withdrawal of my consent to the processing of personal data should be submitted to the headquarters of JCommerce Sp.

However, the withdrawal of my consent shall not affect the lawfulness of processing carried out on the basis of the consent in question prior to its withdrawal

I have the right to access the content of my data, including to receive copies of it and correct it, delete it and limit the processing of it, as well as the right to transfer it, the right to object to the processing of it, and the right to withdraw my consent at any time.

The provision of the aforementioned personal data is voluntary but essential to create a free trial account in the Jamf platform or for marketing purposes if I have chosen the remaining options.

40-114 Katowice – the personal data controller – that:

#JAMF PRO API PRO#

Use the variable with the Bearer Token authentication type selected to perform calls to all other Jamf Pro API endpoints.I have been informed by JCommerce Sp. Now the endpoints can be used to generate, refresh or invalidate tokens.

Navigate to the Variables tab and populate the username, password and URL for your Jamf Pro environment. 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 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 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. The Jamf Pro API supports Bearer Token authentication and uses the standard User Accounts and Groups functionality of Jamf Pro.

Jamf pro api