Custom connector with ID and secret

Hello,

I am new to creating custom connectors, and have been given access to a third party platform's API (given an ID and secret). I also have been given an endpoint from which to obtain a bearer token.

In Power Automate, using the HTTP connector, this works fine with the below...

POST

URI: https://api.platform.com/auth/token

Headers: Content-Type, application/json

Body: {
"grant_type": "client_credentials",
"client_id": "ID_value",
"client_secret": "secret_value"
}

The endpoints to then use this bearer token against are like "https://api.platform.com/v1/departmentdata" and this all works fine.

When I try to create a custom connector, I put the Host as https://api.platform.com and the base URL as /. Then on the Security screen, I am selecting the OAuth 2.0 auth method and the identity provider as Generic Oauth 2. I put the client ID as the ID value, and the Client secret as the Secret value. I put https://api.platform.com/auth/token as the Authorization URL, and the Token URL and the Refresh URL, and leave scope blank.

I create the 'departmentdata' definition (which is a GET) and save. But then I try to create a connection in the Test pane, it just pops up with a "Hmmm... can't reach this page" error.

Is there some kind of redirection that the API provider needs to support? Is there any way around this? It will be hard for my client to understand that we can access the API fine via straightforward HTTP requests, but not when creating a custom connector.

Thank you in advance!

Categories:

Authentication

Quick Links

Leaderboard > Power Automate - Connector Development