What are you trying to achieve?
I was trying to post on LinkedIn organization with the admin profile but getting error for not fetching the organizations list it is showing that “Failed to Load” and status code is “400: Invalid query parameters passed to request”. I have tested this a week ago but now it start showing the error regarding organization list.
Steps taken so far
I have tried all the steps that are been given in the community and ChatGPT (Check connection status, Connect again, admin page and authorization, refresh each and everytime) but this problem is not getting solved. If somebody have faced the similar issue and solved it please let me know.
1 Like
Welcome to the Make community!
What API endpoint are you calling on bridgedataoutput.com? Do you have a link to the official documentation?
If you need assistance in setting up the app’s universal module, or the built-in generic HTTP modules, please provide additional information about what you have tried in relation to the external service’s Developer API Reference — how you are setting the connection up, a link to the endpoint are you trying to connect to, and what errors you are encountering.
You can also complete this brand new course/tutorial in the Make Academy on how to use external APIs — API calls with HTTP modules
- API and Endpoints
- Header and body
- Multipart/form-data
- OAuth 2.0
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
Having same Issue.
It worked flawlessly last year with Multiple connected accounts.
3 Likes
Same issue here! Seems like a problem to exist since March 19
1 Like
Welcome to the Make community!
Since there are multiple users having the same issue at the same time, it’s most likely a bug.
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. Make support has access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free Make account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
4 Likes
Hi,
I’m facing exact same issue. I have double checked the connection and re-authenticate LinkedIn.
Publishing to personal page works fine.
So I do have both as seen on the picture - personal and Org. I’m the only Superadmin in my Org’s page.
I have been struggling this issue as well. After trying everything, I opened a support ticket. Sounds like it is now a known issue and Make developers are working on it:
"We do not have an ETA for this yet, but rest assured, our team is prioritizing this issue.
As a workaround, you can map the Organization ID value after enabling the “Map” slider for now as shown in the below screen-shot.
I will get back to you once the developers provide further updates"
The advice from support FINALLY worked!!
Essentially, using the LinkedIn (OpenID Connect) module, you have to map the org ID by sliding the Map slider. Here are the steps:
First, Find the org id from your company page:
Second, slide the “Map” option and paste the org id here:
NOTE: the org id has to be posted IN THIS FORMAT “urn:li:organization:xxxxxxx”
This worked for me, thankfully.
1 Like
Unfortunately, I still get the same error, even with mapping. Can anybody relate?
Hello everyone @here, thank you very much for raising this in the community.
I just wanted to confirm that we are aware of this issue and that our development team is actively investigating it. We’ll make sure to share any updates as soon as they become available.
We genuinely apologize for any inconvenience and disruptions this may have caused.
Thank you very much for your patience and understanding. 
3 Likes
Hello everyone @here
Thank you very much for your patience as we worked on resolving this.
The dev team has confirmed that the issue is now fixed, and the LinkedIn modules should function as expected.
Please test on your end to make sure everything is working for you.
Thank you very much for your cooperation
2 Likes
