Issue with Creating OAuth Connection Using Make.com API

Questions
, ,
1

Hello Make.com Community,

I’m having trouble using the Create Connection API when working with OAuth connections. For non-OAuth connections (e.g., accountType: "basic"), everything works fine. However, when I attempt to create a connection with Wild Apricot (which uses OAuth), I encounter issues. Here’s what happens:

Steps I Took:

  1. Used the Create Connection API:
  • Endpoint: /v2/connections?teamId=
  • Request body:
{
    "accountName": "WA Connection",
    "accountType": "wild-apricot",
    "scopes": [
        "auto"
    ],
    "apiKey": key
}
  • Response:
{
  "connection": {
    "id": 3722614,
    "name": "WA Connection",
    "accountName": "wild-apricot",
    "accountLabel": "Wild Apricot",
    "packageName": null,
    "expire": null,
    "metadata": null,
    "teamId": 740188,
    "theme": "#0f9d58",
    "upgradeable": false,
    "scopes": 0,
    "scoped": true,
    "accountType": "oauth",
    "editable": true,
    "uid": null
  }
}

However, no connection is created in my Make.com account. This makes sense since Wild Apricot requires OAuth, which involves verification and authorization.
2. Attempted OAuth Authorization:

  • I used the /v2/oauth/auth/{connectionId} endpoint in my browser to obtain an authorization token or URL.
  • The browser displayed a message saying, “Close this window to continue,” but nothing happened afterward.

My Question:

How do I properly create and authorize an OAuth connection using Make.com’s API?

Specifically:

  • Is there a way to trigger the OAuth authorization flow after creating the connection?
  • How can I use the /v2/oauth/auth endpoint to authenticate via the 3rd party service?
  • Are there additional steps required to make this work?

Any guidance on how to resolve this would be greatly appreciated. Thank you!

2

Hey @Jonathan_Avraham

Wild apricot uses simple APi Key authorization. Hence, you just need to grab your api key and put it into Make. That’s it.

image
image1025×493 71.5 KB

Regards,
Msquare Automation - Platinum Partner of Make
@Msquare_Automation

3

Yes, I do not have a problem connecting to Wild Apricot via Makes User Interface, I have an issue connecting to it via the API thats given which is what I need.

4

Have you programmed the make api outside of Make?

5

@Darin_Patterson can you help here? Seems we are stuck. I’m working with @Jonathan_Avraham on a full node js front end that controls make via the Make API.

6

Yep – I think this response of mine will help a great deal: Make API: Numerous issues with Create connection - #8 by Darin_Patterson

Have you had a chance to review and try out those steps?

7

@Darin_Patterson I don’t think your suggestions take into account that all API calls are being done without the Make UI. We are testing this from Postman - I am working with @Jonathan_Avraham on this.

8

For clarity, the link I provided is definitely about creating connections outside of Make.
All the same principles apply (…coincidentally you can, of course use Make to do it as well).

10

Looks like we needed to add the /test endpoint to “test” and confirm the connection after creation.