Using Session Auth method with a client_id and secret_id

Well, I was able to solve my problem myself, so I will explain how I did it in case someone else needs it.

I will show you the way I connected my API with only a POST call to get a token that require a client_id and a client_secret. So you don’t need an Authorization URL nor than a test call.

I did my connection with the roller API (https://docs.roller.app/), if you use another API (Which is very probable), some manipulation may differ a bit but I assume you’ll be able to manage them.

Let’s start,
the authentication method you need to use is Session Auth. Select it and click on Save.

We’ll first add some fields that’ll be useful for after:
    - The Client id (Field type: Field, Key: client_id, Required, Type: password)
    - The Client secret (or secret id, check your API documentation) (Field type: Field, Key: client_secret, Required, Type: password)
    - The token (Field type: Computed Field, Key: The same name as the one referenced in your token POST call documentation, in my case it’s access_token.)

Here’s an example how I do a field:

It supposes to be approximately looking like that:

We’ve finished setting up the Step 1, let’s go for the Step 2.

This will be the part that the most differ since the POST call you have depends on your own API.
Here’s the instruction that my API gives me: https://docs.roller.app/docs/rest-api/ZG9jOjcxNDEwMzc-authentication

We can see the access_token and the token_type on this screenshot, this is the reason why I named my keys this way, to make them match. This is really important to make them matching (It’s even case-sensitive) or it will not work, be careful.

First, let’s write token POST call URL:

When you’re done with that, click on Show Options button. It normally shows something like that:

Replace the body values by what you need (Your documentation is supposed to tell you this). Whatever your documentation tells you, make sure to put the variables we created before, the way that {{bundle.authData.client_id}} correspond with your client_id field and {{bundle.authData.client_secret}} correspond with your client_secret field. In my case, the documentation tells me to create a body like that:

Body - {"client_id":"xxxxxxxxxxxxxx","client_secret":"xxxxxxxxxxxxxxx"}

And this how it looks for me:

Go then to the HTTP Headers tab and modify it according to your API documentation. For me, I start with this:

And end up with this:

Think to modifying your URL Params tab if you have to. In my case, I don’t need to.

We’ve finished setting up the Step 2, let’s go for the Step 3.

For this step, I don’t have any test request available in my API (But if you have one I’ll recommend you to use it of course). If, like me, you don’t have a test request, we’ll simply bypass the issue by using a random GET API call available in our documentation. I personally decided to use this call: https://docs.roller.app/docs/roller-api/67bddadddf571-get-customers

The only thing we need, is make sure that the call will not fail, and successfully return a 200 HTTP Code, Zapier will recognize this call as successful test.

Same as the step 2 paste the API call URL and also click on Show Options button:

You will be normally in the URL Params tab. This should be a bit messy, so remove everything, and set the parameter (Params) your API call require (Refer to your own documentation).

These are the parameters I need for my request, but I will only set the ones that are marked as required.

This is how it looks for me:

You also need to set the HTTP Headers tab that should be also messy.

This must be here where you need your token, so don’t forget to use the variable {{bundle.authData.access_token}} (Where access_token is the name of the key corresponding to the field of your token. We set up in the first step, don’t forget to have a name that match with the one you get in the token call). This look like this for me according to API documentation:

After you’ve done that, you normally ended the step 3. But make sure you didn’t have forgotten anything that I don’t mentioned because I don’t need it in my call, but not in yours.

Don’t forget to click on the button Save & Continue !

We’ve finished setting up the Step 3, let’s go for the Step 4.

This last step is the easiest of all, start by just clicking on this big blue button that start with “Sign in to the_name_of_your_integration” :

Fill the fields with the values you need:

And click on Yes, Continue. It will normally close after few seconds, if not, you may have an error message, in this case make sure you correctly followed all the step of the tutorial, and check that your request are made accordingly to your API.

Then click on the button Test Authentication and you normally got a little notification saying:

“Request Successful”

If that’s the case, congratulation, you’ve made it! 👏
You just have to click on Save & Finish.

In other case, good luck 👍. (Joking, feel free to ask questions.)