1 ACCEPTED SOLUTION
Yes, updating the name is supported. Make sure to check the center column of the documentation to determine what inputs are allowed by the endpoint you're referencing. The right column, which you included a screenshot of provides an example of a successful response (not the request). I've included a screenshot for reference, which shows that "name" is a supported element in the request body:
The following format is a valid request body:
{
"general": {
"name": "NewDeviceName"
}
}Finally, the error you're getting seems to be unrelated to the request body. 404 means that the server couldn't find the resource that you specified, in this case, the device ID. Make sure the variable you're using is set properly and/or being passed properly. If you're not super familiar with an API operation or the coding language, it's generally a good idea to ensure the code you're writing works first with hardcoded values, then work backwards to make it scalable/reusable, by substituting in the variables.
Hi @chadlawson,
Thanks for the suggestions. The issue seems to be with making the correct path to access specific data via the new API (UAPI). If you open it via https://jss.COMPANY.com:8443/uapi/doc, you can open up the "computers" just like with the old API and here is the result of the new API for example, one of the machines:
{ "totalCount": 436, "results": [ { "id": "2519", "location": { "username": "USERNAME", "realName": null, "emailAddress": null, "position": "", "phoneNumber": null, "department": null, "building": null, "room": "" }, "site": null, "name": "NAME", "udid": "F093F85C-7A4E-58BE-B0ED-21219C07A6C4", "serialNumber": "C07VR6GXG1HW", "operatingSystemVersion": "10.13.1", "operatingSystemBuild": "17B1003", "macAddress": "XXXXXXXXX", "assetTag": "", "modelIdentifier": "Macmini7,1", "mdmAccessRights": 0, "lastContactDate": "2020-08-19T14:26:20.39Z", "lastReportDate": "2020-08-19T09:05:13.661Z", "lastEnrolledDate": "2019-12-26T19:42:44.538Z", "ipAddress": null, "isManaged": true },
What I am trying to do is by using udid or serial # (doesn't really matter), obtain machine's name on the JSS. Using your example, I put this together, which seem to be locating the machine, but the data it produces is weird... Here is the code (the path I basically copied directly from UAPI, I have included 2 screenshots directly from there, so it will make more sense):
compserial=$(system_profiler SPHardwareDataType | awk '/Serial Number/ {print $NF}')
echo $compserial
computerinfo=$( /usr/bin/curl "$jssurl/uapi/preview/computers?page=0&size=0&pagesize=0&page-size=0&sort=name%3Aasc/${compserial}" --silent --request GET --header "Authorization: Bearer $token")
echo $computerinfoThe result I get:
} ]Managed" : true,: "2019-04-26T17:58:37.746Z", 300""ence",
I thought I was suppose to get full information on a specific machine based on the serial # and then grab from that data it's ID by modifying the curl string, but what I am getting is information that machine is "Managed" + "lastEnrollmedDate" ("2019-04-26T17:58:37.746Z"), I am not sure what 300 and ence is. Appreciate any other ideas.
@pshaik , 401 - is authentication failure, make sure you can authenticate with your token on the UAPI web page itself: https://jss.YOURCOMPANY.com:8443/uapi/doc/
For example, in here it fails:
See if you can authenticate on that page first.
@SamF, you have been very helpful with this, maybe you can help me out with this one. I was able to get and update extension attributes data, but can't sort or update (PATCH) the site... is it something still not supported or am I doing it wrong?
Trying to sort by sites:
siteslist=`curl --request GET \
--url "https://jss.MYCOMPANY.com:8443/uapi/v1/computers-inventory?section=GENERAL&page=0&page-size=100&sort=id%3Aasc&filter=site" \
--header "Accept: application/json" \
--header "Authorization: Bearer $token"`
echo "siteslist is: $siteslist"
Getting error: ""No property site found for type ComputersDenormalizedEntity!""
When trying to PATCH/change site:
curl --request PATCH \
--url "https://jss.MYCOMPANY.com:8443/uapi/v1/computers-inventory-detail/$id" \
--header "Accept: application/json" \
--header "Authorization: Bearer $token" \
--header "Content-Type: application/json" \
--data '
{
"general":
{
"site":
{
"name" : "APAC - Bangalore"
}
}
}
'
Getting: ""Unrecognized field \"site\" (class com.jamfsoftware.computersinventory.api.update.ComputerGeneralUpdateDto), not marked as ignorable""
I was able to obtain and PATCH extension attribute, which is under GENERAL, the same way site is, but can't get it to work with the site... For example, this curl updates the exetnsion attribute as needed per definitionID:
curl --request PATCH \
--url "https://jss.MYCOMPANY.com:8443/uapi/v1/computers-inventory-detail/$id" \
--header "Accept: application/json" \
--header "Authorization: Bearer $token" \
--header "Content-Type: application/json" \
--data '
{
"general":
{
"extensionAttributes":
[
{
"definitionId": "67",
"values": ["'$currentlocaladminpass'"]
}
]
}
}
'
I just don't understand what is the difference as per: https://developer.jamf.com/jamf-pro/reference/computer-inventory-1#get_v1-computers-inventory , in the example field on the right you can see the site (see attachment please), unless somehow this is not supported yet...
Since I continue to explore the UAPI :). do you know by any chance if PATCHing computer name on JSS is not available yet as well?
As I get 404 error when trying to do it:
curl --request PATCH \
--url "https://jss.MYCOMPANY.com:8443/uapi/v1/computers-inventory-detail/$id" \
--header "Accept: application/json" \
--header "Authorization: Bearer $token" \
--header "Content-Type: application/json" \
--data '
{
"general":
{
"name" : "'$computernameinput'"
}
}
'
Yes, updating the name is supported. Make sure to check the center column of the documentation to determine what inputs are allowed by the endpoint you're referencing. The right column, which you included a screenshot of provides an example of a successful response (not the request). I've included a screenshot for reference, which shows that "name" is a supported element in the request body:
The following format is a valid request body:
{
"general": {
"name": "NewDeviceName"
}
}Finally, the error you're getting seems to be unrelated to the request body. 404 means that the server couldn't find the resource that you specified, in this case, the device ID. Make sure the variable you're using is set properly and/or being passed properly. If you're not super familiar with an API operation or the coding language, it's generally a good idea to ensure the code you're writing works first with hardcoded values, then work backwards to make it scalable/reusable, by substituting in the variables.
