Why Does the LinkedIn-Get-Member-Organization-Access-Control Tool Return a "Bad Request" Error and have a Broken Documentation Link?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

In the linkedin app queries for the linkedin-get-member-organization-access-control tool returns the following error:

"[debug] err.response {\n  \"status\": 400,\n  \"statusText\": \"Bad Request\",\n  \"headers\": {\n    \"content-type\": \"application/json\",\n    \"x-restli-gateway-error\": \"true\",\n    \"date\": \"Sat, 21 Jun 2025 22:29:45 GMT\",\n    \"x-li-fabric\": \"prod-lor1\",\n    \"report-to\": \"{\\\"group\\\":\\\"network-errors\\\",\\\"max_age\\\":2592000,\\\"endpoints\\\":[{\\\"url\\\":\\\"https://www.linkedin.com/li/rep\\\"}],\\\"include_subdomains\\\":true}\",\n    \"nel\": \"{\\\"report_to\\\":\\\"network-errors\\\",\\\"max_age\\\":1296000,\\\"success_fraction\\\":0.00066,\\\"failure_fraction\\\":1,\\\"include_subdomains\\\":true}\",\n    \"transfer-encoding\": \"chunked\",\n    \"connection\": \"keep-alive\",\n    \"x-li-source-fabric\": \"prod-lva1\",\n    \"x-li-pop\": \"prod-lva1-x\",\n    \"x-li-proto\": \"http/1.1\",\n    \"x-li-uuid\": \"AAY4HIQABKYzQwQ9W9aFbw==\",\n    \"set-cookie\": \"bcookie=\\\"v=2&3a67342f-df6e-4586-89a3-af6df08e7ff2\\\"; domain=.[linkedin.com](http://linkedin.com); Path=/; Secure; Expires=Sun, 21-Jun-2026 22:29:45 GMT; SameSite=None, lidc=\\\"b=OB91:s=O:r=O:a=O:p=O:g=5471:u=1197:x=1:i=1750544985:t=1750613979:v=2:sig=AQF745RzjprJInYsq0QC3n4QyWU29H-F\\\"\",\n    \"x-li-route-key\": \"\\\"b=OB91:s=O:r=O:a=O:p=O:g=5471:u=1197:x=1:i=1750544985:t=1750613979:v=2:sig=AQF745RzjprJInYsq0QC3n4QyWU29H-F\\\"\"\n  },\n  \"config\": {\n    \"transitional\": {\n      \"silentJSONParsing\": true,\n      \"forcedJSONParsing\": true,\n      \"clarifyTimeoutError\": false\n    },\n    \"adapter\": [\n      \"xhr\",\n      \"http\",\n      \"fetch\"\n    ],\n    \"transformRequest\": [\n      null\n    ],\n    \"transformResponse\": [\n      null\n    ],\n    \"timeout\": 0,\n    \"xsrfCookieName\": \"XSRF-TOKEN\",\n    \"xsrfHeaderName\": \"X-XSRF-TOKEN\",\n    \"maxContentLength\": -1,\n    \"maxBodyLength\": -1,\n    \"env\": {},\n    \"headers\": {\n      \"Accept\": \"application/json, text/plain, **/**\",\n      \"Content-Type\": \"application/json\",\n      \"Authorization\": \"Bearer [REDACTED]\",\n      \"X-Restli-Protocol-Version\": \"2.0.0\",\n      \"Linkedin-Version\": \"202409\",\n      \"User-Agent\": \"axios/1.10.0\",\n      \"Accept-Encoding\": \"gzip, compress, deflate, br\"\n    },\n    \"url\": \"https://api.linkedin.com/rest/organizationAcls?[object Object]\",\n    \"allowAbsoluteUrls\": true,\n    \"method\": \"get\"\n  },\n  \"data\": {\n    \"status\": 400,\n    \"code\": \"ILLEGAL_ARGUMENT\",\n    \"message\": \"Invalid query parameters passed to request\"\n  }\n}"

Also, the documentation link in the tool description leads to a 404 error page.

2

Looks to me like the URL being passed in the tool is invalid:

https://api.linkedin.com/rest/organizationAcls?[object Object]

Should be:

https://api.linkedin.com/rest/organizationAcls?q=roleAssignee

3

Hey , could you do us a favor and report this issue in our public repo?

  1. Head over to Support - Pipedream
  2. Click on the “Request an Integration” card.
  3. Select “B - Request changes to an existing integration.”
  4. Fill out the form with details of the issue.
    This way, it gets logged in our public repo, and the component development team can be notified!