LinkedIn Updated API OAuth system

[julian10]

Hi,

Julian here. I’m new to Bubble.io but loving what I’m experiencing so far.

I’d like to sign users up using LinkedIn via the API Connector, as I need their email addresses.

Although this topic has been covered previously, there have been recent changes to the LinkedIn OAuth system that I don’t think have been covered elsewhere, and I’m struggling to make a successful connection.

I’d be grateful for any help to get this working.

Here’s my API Connector settings:

And here’s the error I get after signing in to LinkedIn:

Thanks🙏

[Jici]

In user id keypath, set sub instead of id

[julian10]

Amazing!!! Works

Thank you🙏

[julian10]

Next challenge… How to set up the API Calls and the specific GET requests to gain access to the LinkedIn personal data fields, including email address.
All/any help is appreciated

[Jici]

Put the same thing that you have in user profile endpoint.

[julian10]

Thank you. It’s working fine now

[cedrikpendji]

hi Julian. How did you solve it? I’m able to successfully sign up users from Linkedin but I can’t get the GET call to retrieve user info to work. Please have a look at my settings here. I can’t initialize the call and always get the error message attached

[Jici]

The first step is to initialize the auth. Look at the message in the auth section. Create a dummy page with action Login with social network in debug_mode to initialize the auth. After that, you will be able to initialize API call.

[julian10]

As @Jici says.

[cedrikpendji]

I tried that. As you can see in the screenshots below, I was able to authenticate. Although i receive a bubble message saying “this user already exist” as the email associated with my linkedin is already a user in my APP. But after all this, I still can’t initialize calls. Is there something I’m missing?

[julian10]

I am no expert with APIs but here’s what I see different in your set up compared to mine.

I hope this helps!

[cedrikpendji]

It’s working now. I don’t know what was the issue. All I did was reordering the order of the parameters in the Scope.

[cedrikpendji]

I am now struggling to initialize a post call. I believe the issue might be with the parameter “author”, i’m not sure how to set it up. @Jici @julian10 Can you please have a look at my settings below and tell me what i’m doing wrong? You can see below the error message

[Jici]

From what I read, ugcPosts is deprecated,
you should use

Posts API - LinkedIn

Are you sure you use the correct ID ? In documentation, the ID seem to only use numeric chacaters…

Look at:

Linkedin API Connector Post

Hi, Did you mange to find solution ?

[cedrikpendji]

Thank @Jici . I’ll read the Posts API - LinkedIn documentation and update my settings accordingly.
For the id, which one should I use? If my LinkedIn url is https://www.linkedin.com/in/cedric-rivera/. So my ID would be “cedric-rivera”, correct? and the value of author should be urn:li:member:cedric-rivera?

[Jici]

It’s hard to find info about that, but try to do a get request to
https://api.linkedin.com/v2/me

and use the ID provided in urn:li:person:yrZCpj2Z12

[cedrikpendji]

Thank you very much @Jici .I was able to get my correct id after making the GET request. And after I was able to initialize the POST call.
Much Appreciated!

[insalman360]

Hey @cedrikpendji, could you explain how you did that with/without author id?