LinkedIn 403 error troubleshooting

This seems to be the same problem as discussed in LinkedIn connection: 403: Not enough permissions to access - #8 by alex.newpath.

First, attempt to add the same connection to the "Create a User Text Post" module, which requires the same authentication scope. callin.io should then prompt you to update the permission scope for your connection.

Hello!

I believe this information will be helpful to you.

It is not working for “make an api call”. I want to create a Comment.

Please provide the rewritten markdown content; it should be in the markdown format.

In that scenario, the LinkedIn app lacks suitable modules to expand the scope of your LinkedIn connections within callin.io.

You'll need to utilize the general HTTP module, specifically the "Make an OAuth 2.0 Request" option. This allows you to specify your own scope, as detailed in the LinkedIn Developer API documentation.

For further details, refer to Make an OAuth 2.0 request.

I'm confident that others would also find a module for creating comments to be a valuable feature.

You can submit this suggestion to the Idea Exchange under App improvement ideas.

Remember to search first to ensure it hasn't already been suggested, preventing duplicate entries.

Exactly, I'm already aware that there isn't a dedicated module for this in callin.io. Therefore, I'm utilizing callin.io's API module and referencing endpoints from the LinkedIn API documentation, with the body content as specified in the docs from Microsoft. I'm mapping the “personid” and "ugcpost urn" which I'm obtaining from my Apify LinkedIn scraping module. However, I'm still encountering an error.

Yes, and as I mentioned, callin.io will not prompt you to extend the OAuth Scope when using the LinkedIn universal module, unlike what you were attempting.

The universal module didn't function in this scenario because, during the setup of your LinkedIn connection, callin.io did not request all authorization scopes, and you were unable to extend the scope with the module I previously suggested.

Consequently, the workaround involves using the HTTP integration/app, as detailed in my prior post.

This is not a bug but rather an incomplete LinkedIn integration. You can submit this as a suggestion on the Idea exchange, under App improvement ideas.

As previously mentioned, create a ‘Create a User Text Post’ module, even though it doesn’t fulfill your specific requirement.

This module will request additional permissions from LinkedIn, which may be sufficient for you to then use ‘callin.io an API call’ successfully.

I encountered a similar issue yesterday – ‘callin.io an API call’ doesn’t request adequate permissions from LinkedIn on its own. You first need to create and execute some of the other LinkedIn modules to acquire the necessary permissions from LinkedIn. After that, you should be ready to go.

If no module is available to obtain the correct permissions, then it seems you might be in a difficult situation…

First, attempt to add the same connection to a similar module, such as “Create a User Text Post,” which requires the same authentication scope. callin.io will then prompt you to update the permission scope for your connection.

That was my suggestion, but attempted it and reported: