Power Platform Community Forum Thread Details

I'm hoping someone else has run into this situation and knows the perfect solution! I want to build a custom connector to the Filevine API, but I noticed in the documentation that opening a session requires a hash calculation based on the key, secret, and a timestamp. Is there a way in our custom connectors to include a quick calculation, or do I need to deal with this through a flow?

Thanks in advance,

Bryan

Categories:

Connector development

Got this one solved with a massive amount of assistance from @StalinPonnusamy (all the kudos to him!), and here are the high-level pieces for those looking to deal with this or similar APIs:

The Filevine API requires an MD5 hash of a string consisting of the API Key, API Secret (set up in Filevine's portal), and an ISO-formatted timestamp (make sure it has 3 decimal places in the seconds). We got this done using a C#-based Azure Function that is accessed using its own custom connector. It returns the MD5 hash value that is used in Step 2.
Build second custom connector specifically to access the Create Session API GET call in the Filevine documentation. This call requires the API Key, plus the MD5 hash and timestamp used in Step 1. This is a non-authenticated API call that when successful will return an orgId, userId, accessToken, and refreshToken
Use an HTTP call to make further calls to the API using the four response parameters from Step 2. Authorization on subsequent calls is done using the accessToken as a bearer token, with userId and orgId also passed through the header. The refreshToken is passed through the header using the key of "x-fv-sessionid"

Bryan