Question? Has Jamf changed his Classic API Syntax?
Example: When making a simple get Command using the following syntax
curl -su example:exmaple -H "accept: text/xml" https://example.jamfcloud.com/JSSResource/computers/
I get the following error message:
<title>Status page</title>
</head>
<body style="font-family: sans-serif;">
<p style="font-size: 1.2em;font-weight: bold;margin: 1em 0px;">Unauthorized</p>
<p>The request requires user authentication</p>
<p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2">here</a>.<br>
Please continue your visit at our <a href="/">home page</a>.
</p>
</body>
</html>%
However if I just cut and past from the try this out I notice that url now has a bearer token attached to the end.
Example curl -X 'GET' \\ 'https://example.jamfcloud.com/JSSResource/computers' \\ -H 'accept: application/xml'
I don't see the deference!? ¯\\_(ツ)_/¯