Scripting

Hi @SeRil,

I think the latest versions of the SMA utilizes JWT authentication method. Thus, you will see 'x-kace-authorization' in the header containing the bearer token. For authentication, try this:

1. POST request to http://mykace/ams/shared/api/security/login with username and password (ensure 'Mobile Device Access' is enabled for designated/service user, Settings > Users )
   Retrieve responded header ['x-kace-authorization'] and cookies. Cookies should contain your logged session and kbox info. These are required and to be included for subsequent API calls.
   
   
2. Try GET request to http://mykace/api/users/users/ 
   
   Good luck as I think this is sufficient for you to start! 

What programing language are you using to make the API calls?

Or are you using Postman?

Hi ! I am using Powershell, but also a "manual" REST client called Boomerang (Chrome Extension), similar to Postman.

Thank you so much for your answer, it was a huge help!

I managed to re-use the cookies, and actually got data with :

- http://mykace/api/users (but not with http://mykace/api/users/users)

- http://mykace/api/machines (but not with http://mykace/api/inventory/machines)

The most problematic part is that "api/machines" is indeed returning a list of machines, but I have no documentation on how to handle those. I tried following the same rules as for the theoretical "/api/inventory/machines" (from https://support.quest.com/de-de/technical-documents/kace-systems-management-appliance/12.0%20common%20documents/api-reference-guide#TOPIC-1681523), but it doesn't work the same : with "/api/machines", I can't use filters, nor append a "/{id}", it just keeps returning the same array.

The API version returned is "16". Is there any reference guide to help me somewhere ? 

I trying to get api with normal /api/users/users BUT got an error 401 Unauthorized .
any suggestion ? 

with error 

errorDescription" : "Authorization tokens could not be found"

KACE SMA version 13.1 

Same problem here but I think it is related to the use of 2FA.
I tried following the indications in the documentation but with no success:

When 2FA (multifactor authentication) is enabled, an additional step is required, to supply the security code after obtaining the KACE_CSRF_TOKEN. Failing to do so causes all future API calls to be invalid with an HTTP status of 401, and the following body:
{
    "errorCode": -1,
    "errorDescription": "User not fully authenticated."
}

You can supply the 2FA code through a POST request at /ams/shared/api/security/verify_2factor. For example, if the appliance name is KACE_SMA_Test, the route to supply the code is: http://KACE_SMA_Test/ams/shared/api/security/verify_2factor.

The body for the POST request must contain the current code from 2FA. For example:
{
    "currentCode" : "codefrom2fa"
}

If the code supplied Google Authenticator is 123456, you can use the following statement:
{
    "currentCode" : "123456"
}

The header for this request must contain x-kace-api-version.

When a success is received, the custom API call no longer returns the authentication error:

If the security code is valid, the API call returns the HTTP status 200, with the following body:
{    "Result": "Success" }

Once the security code is accepted, all future API calls should function as expected.

When I try to launch another post request (I'm using Postman just to learn to use Kace APIs) using same Params but only currentCode in body (raw-Json) I obtain an error:

{
    "errorCode": -1,
    "errorDescription": "Invalid API version header."
}

In all honesty I don't know what I am doing wrong. I have already checked the cookies and the header part but it is inherited from the first Put.

I'm getting the same {"errorDescription" : "Authorization tokens could not be found"} response. I'm logging in with this:

curl -v -X POST "https://HOSTNAME/ams/shared/api/security/login" -H "Content-Type: application/json" -d "{\"userName\":\"MYUSER\",\"password\":\"MYPASSWORD\"}"

And I get a 200 OK response, the body being JSON describing my user. And in the header response:

x-kace-authorization: Bearer eyABIGLONGTEXTAUTHCODEGOESHERE

So then I'm using that to make a request:

curl -v -X GET "https://HOSTNAME/api/service_desk/queues/" -H "x-kace-api-version:16" -H "Accept: application/json" -H "x-kace-authorization: Bearer eyABIGLONGTEXTAUTHCODEGOESHERE"

I tried "Authorization: Bearer" and "x-kace-auth-key: Bearer" as well, but all just gave me the "Authorization tokens could not be found" 401 Unauthorized response.

And when I try: https://kace.ericksoninc.com/api/service_desk/tickets/ instead, I get:

{"errorCode":-1,"errorDescription":"No Current Organization Selected"}
So I tried passing in , \"organizationName\":\"Default\"} to the initial Login, but still get the same errors for both calls.  Am I missing something? Thanks!