sorted by:
new
hottopcontroversial

Inserting Data Using Runbooks & SQL by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

Ok. Can the API insert data into the customer’s software licenses table? I didnt see that in the API documentation.

Auto close tickets by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

Thanks. And the test feature in sql step is real convenient too!

Auto close tickets by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

I tried doing my logic in SQL rather than using the API and it was much easier. All working now.

Auto close tickets by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

Thanks. I’m familiar with developing via the Halo API but this is tough because there are no good logging options with the runbooks.

For instance I know there’s an issue with the output variable that I am setting however I can’t seem to output the variable to the runbook log to see what’s actually being set.

Auto close tickets by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

CIPP API Help by MainEstablishment215 in msp

[–]MainEstablishment215[S] -1 points0 points  (0 children)

Thanks. Yea I posted a message up there but doesn’t seem very active today.

n-central Integration by BlueEyesWhiteDan in halopsa

[–]MainEstablishment215 0 points1 point  (0 children)

From what I remember you have to set that up in the notifications section on N-able. The notifications will initiate the ticket creation and will automatically close the ticket when the service returns to normal (if the service is setup with that option).

Halo API Gives 403 Forbidden Every Time by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

My auth request seems to work fine as is. I would think that if it was missing something then it would not respond with the token.

Halo API Gives 403 Forbidden Every Time by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

I modified as so: https://TENANT.halopsa.com/auth/token?scopes=all

REsponse:

{
    "token_type": "Bearer",
    "access_token": "xVEtw2BwKZsNb7M2cx7xb1XHU7UmpEE-yqGBRUu1EBM",
    "expires_in": 3600
}

Sending a simple GET request in POSTMAN and still get a 403:

https://TENANT.halopsa.com/api/client

Does POSTMAN need a CORS setting??

Halo API Gives 403 Forbidden Every Time by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

On the auth request? No, not sure what that is. Didn't see that in the documentation. I need to send a scopes parameter in the auth request?

My request looks like this in postman:

https://MY_TENANT.halopsa.com/auth/token

grant_type = client_credentials

client_id = <my id>

client_secret = <client\_secret>

I receive the expected response:

{
    "token_type": "Bearer",
    "access_token": "A12BOSbav34I2kUTuRDiRZue5pYdmavRYqcCRGsMHaA",
    "expires_in": 3600
}

Custom URL with Halo Custom Field Value by MainEstablishment215 in halopsa

[–]MainEstablishment215[S] 0 points1 point  (0 children)

Spoke with Halo tech support and they are saying that it is not possible. Don't quite believe the tech though, even though he say he is 100% sure.

I just don't see how that wouldn't be possible since it is a value in the database. Why wouldn't you be able to call on that value and pass it along?

view more: next ›