Modmike
Novice

HotDocs Advance REST API to Service Instance - anyone done this?

Jump to solution

Hi,

 

I'm trying to create a service instance of type REST for incorporating the HotDocs Advance API but not having much joy.

 

I can query the API fine from PostMan but K2 doesn't like the Auth/Token endpoint.

 

In HotDocs Advance the call to get Authorized is as follows:

 

https://hddev.mycompany.com/hdaauth/Authorize/ServicePrincipalLogIn

 

There's a Header : Cntent-Type = application/json
And the payload is RAW JSON in the Body of the request:
{
"ClientName": "K2Client",
"PrincipalName": "K2ClientSvcPrinciple",
"PrincipalPassword": "passwordhere"
}

As I said this works fine in Postman and I can use the returned token in the BODY to authorize all my calls to the API.

HotDocs have said that their API is not "pure OAUTH"... not sure what that means. Does the above look like it will be able to fit into the K2 REST instance type?

Hope someone can assist?

 

Regards,

 

Mike.

0 Kudos
Reply
2 Replies
boringNerd1
Apprentice

Re: HotDocs Advance REST API to Service Instance - anyone done this?

Jump to solution

Hi,


You will most probably need to setup OAuth to get this to work. I am not sure how to go about doing it, because I have never done this before. But, it is possible to use the REST service broker with OAuth. One such example is the K2 and UiPath integration. You can also refer to this document on configuring OAuth to help you.


 

0 Kudos
Reply
Modmike
Novice

Re: HotDocs Advance REST API to Service Instance - anyone done this?

Jump to solution

Hi,

 

It turns out that OAuth is not the solution here. HotDocs Advance is not pure OAuth (whatever that means)

 

I've had some technical guidance from Graham Penman who is a senior technical specialist at K2. He's created some swagger files and you use Impersonation as the authentication method. It's too technical to explain here but I'm at least up and running now!

 

Thanks for pitching in 🙂

 

Mike

0 Kudos
Reply