#Jamf pro api update#
#Jamf pro api Patch#
#Jamf pro api software#
#Jamf pro api mac#

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.

#Jamf pro api update#

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.

#Jamf pro api software#

This was a great learning experience in my software engineering career, and I feel proud to have reached a point in my career where I am not only actively maintaining my team's codebase, but also helping to improve other systems on which we rely.This collection is provided to assist Jamf Pro users of the Classic API. In fact, I had first coded the system to use the Jamf Classic API to ensure that it worked, and then upgraded the call to Jamf Pro API because we needed other Pro API features. Luckily, when I wrote the system design doc for our Asset Management app, I had discussed this with the senior software engineer on our team and we knew that it was safe to use the newer Jamf Pro API because we knew that we could always fall back on the Jamf Classic API. But it's important to factor in risk in our system design docs when leveraging external libraries. As software engineers, we always try to use libraries, API's, and tools that will work properly. The takeaway here is that API's - even from reputable companies like Jamf Pro - can have bugs, and just because an API is in production does not guarantee that it will work properly.

We discussed the issue together, I did testing, and then contacted Jamf Support. A member of the Helpdesk team had first discovered this issue, and then discussed it with our Jamf admin. Here is a screenshot of the changelog with the relevant line highlighted.

#Jamf pro api Patch#

I then noticed that this problem of Jamf computers losing their Filevault encryption was not only when employees were offboarded, but actually when any Jamf computer state changed, which resulted behind the scenes in a name change via the PATCH /computers-inventory-detail/ endpoint. Next, I checked if it could be a result of unmanaging a computer from Jamf this also was not the problem. At first, I thought it was the Jamf device lock command which could be causing the problem, but after some isolated tests where only the Jamf device lock command was issued, I deduced that this was not the problem. I immediately began looking into what the culprit could be. This was a serious security problem because our company data needs to stay protected until the laptop comes back to IT and goes into 30 day hold, before it can be wiped and issued to new employees or e-wasted. I had developed on it while it was on beta and after it was out of beta, mainly out of necessity because it had a few features that the Classic API did not support such as the ability to fetch DEP (Apple Device Enrollment Program) computers so that we could load computers that we had purchased from Apple into our tool.Ī few months ago, my teammates noticed a problem where Jamf computers that had been offboarded were no longer Filevault disk encrypted. In fact, it graduated from beta around a year ago. As you can probably tell, the Jamf Pro API is a lot newer. The Classic API uses basic authentication and XML payloads, and the Jamf Pro API uses modern bearer auth token authentication and JSON payloads. For context, Jamf has two API's: the Classic API and the Jamf Pro API.

The Jamf Pro API moved out of beta to production around a year ago, and I discovered and reported a serious bug that could affect a lot of users. And many other things which are beyond the scope of this blog or that I cannot talk about.Jira issue created for offboarded employee.Asset sheet created with PDF, which IT prints out and attaches to the laptop.For instance, when an employee is offboarded, the following things automatically kick in for each of their laptop(s):

#Jamf pro api mac#

This service ties together Jamf Pro (for managing Mac computers), Jira (for creating IT Helpdesk issues), our SQL database, our People Portal (for onboarding/offboarding employees), and other things with our business logic. One of the internal tools that I have built at WePay is an Asset Management tool which our IT team uses to manage the lifecycle of employees' MacBook Pro work computers.