HTTP - how to access this API with Power Automate?

[Oskarkuus]

I cant figure out how to configure the HTTP connector to access this api

https://apidocs.scrive.com/#oauth

[abm]

Hi @Oskarkuus 

I haven't used this connector but I had a quick look at the documentation. I can see Power Automate have a connector for Scrive.

Signup using the below links:

https://www.scrive.com/get-started-api

https://api-testbed.scrive.com/new/api-requests

Once you signed up you could use the same credentials for Power Automate Scrive connector. I managed to signed up a trail version and successfully created a connection.

Test

https://api-testbed.scrive.com/new/integrations

Live

https://scrive.com/new/integrations

I haven't tried the direct API access to generate the security token using Power Automate HTTP action.

Thanks

[Oskarkuus]

Yes i am currently using the connector for Scrive.

But i rather use the API for some thing since the built connector does not have all the things i want to do.

[abm]

Hi   

Thanks for your reply. I did set up a trail version. I have some success. Here it is

Here api-testbed.scrive.com is the test environment provided by Scrive. For live the endpoint is

scrive.com/api/v2/getpersonaltoken

I have asked the support team and waiting for their reply.

The above step works for me and returned the tokens and secrets.

Below is the step which I am failing to understand how to pass the authorisation element. Currently it fails with invalid auth. Documentation says the below format to use:

Authorization: oauth_signature_method="PLAINTEXT", oauth_consumer_key="123", oauth_token="456", oauth_signature="abc&cde"

Thanks

[Oskarkuus]

Thank you. This helped allot but i am still not quite there...

Step 1:

Get the access tokens

This works.

Step 2:

Parse the JSON response.

This works.

Step 3:

https://apidocs.scrive.com/#list-documents

But it fails on the last step

{

  "error_details": null,

  "error_message": "No valid access credentials were provided. Please refer to our API documentation.",

  "error_type": "invalid_authorisation",

  "http_code": 401

}

[abm]

Hi @Oskarkuus 

That's exact issue I am having. I don't have a license product. I was just curious about this thread and tried via a trial setup. As I mentioned I query the support team about this. There are few emails I exchanged. 

Below is the latest reply.

If you are using a licensed product better contact the support and query this.

Thanks

[Oskarkuus]

That was a frustrating answer.

I have a sales meeting with them tomorrow. I want this if we are going to consider a deal 🙂

[abm]

Hi @Oskarkuus 

I did tried as per the support suggested by passing the below in header but still got invalid auth.

'Authorization: OAuth oauth_consumer_key="REDACTED",oauth_token="REDACTED",oauth_signature_method="PLAINTEXT",oauth_timestamp="0000",oauth_nonce="00000",oauth_version="1.0",oauth_signature="REDACTED%REDACTED"'

This is not a Microsoft Power Automate issue. 

Thanks

[mankirk · Accepted solution]

Hi @Oskarkuus and @abm,
I am the developer that built the Scrive Power Automate connector. I might be too late to the party here but hopefully I can help someone in the future if nothing else.

I would recommend using the Scrive connector to the furthest extent possible but where that is not possible you can use HTTP to manually config the requests. You were on the right track here but the auth header is somehow malformed. I got it working by setting an "Authorization" header like this:

oauth_signature_method="PLAINTEXT",oauth_consumer_key="aaa",oauth_token="bbb",oauth_signature="ccc&ddd"

aaa=apitoken
bbb=accesstoken
ccc=apisecret
ddd=accesssecret

The resulting action looks like this:

Successful run with the full flow:

Hope this helps!

[abm]

Hi @mankirk 

Appreciated the reply. Thanks again.

[ofcourse]

hello everyone
Does anyone have an idea if the grant_type is already accessible on Microsoft. I have been trying for several days to retrieve a token based on the grant_type encoding but it does not work. the same error message yet in postman everything works fine. {"error":"unsupported_grant_type","error_description":"This grant_type is not supported. Please use client_credentials."}