With the ID number in hand, we can use the “Find Computer Search by ID” API endpoint ( /JSSResource/advancedcomputersearches/id/:id) to pull back the XML of that search. To do this we will need the ID number of our Advanced Search (ID can be found in the URL of your advanced search, like: id=6). Investigate the Dataīefore we get too far down the rabbit trail, we will need to understand where the serial numbers are in the response body of an Advanced Search, and how far they are nested.

This could be testing the response code that is returned to make sure the request ran, or it can be storing your results for use in the next request in a Runner (which is what we will be doing). Similar to the Pre-Request Scritps tab, the Tests tab allows you to utlize JavaScript to perform actions after the request has run. We did it this way so that we did not change the Params tab of the request and hardcode the ID variable so we can use the request in a runner later. set to set the “id” variable to the ID of a policy.

In that instance we used the command pm.environment.

We used a pre-request script in Part 2 when we briefly talked about using variables. A Pre-Request Script can allow us to set variables before the running of a request. Postman provides two features that allow us to utilize JavaScript to manipulate data, either before or after a request: Pre-Request Scripts and Tests. To do this we will need an Advanced Search in Jamf Pro to capture our devices and in Postman we will use two API endpoints: “Find computer search by ID” and “Update computer by SN”. Our use case, for this post, is to update the PO Number on a group of computers that we will gather using an Advanced Search in Jamf Pro. Sure, we can run a search, export the data as a CSV, and then use that CSV to feed a runner, but what if we could grab a search in Postman and parse out the devices we want to update? I went down this rabbit trail today and wanted to share the results with you. Maybe we want update a list of devices with PO Number or some other data. Often times we want to perform an action on more than just one object. In this post I’m going to expand a little on our use of the Runner functionality which I covered in Part 4 and Part 5. In my previous posts about Postman I showed you how to setup Postman for working with Jamf Pro, how to create and update policies, how to gather our queries into collections, and much more.

Textexpander 4 serial number