LinkedIn API integration via Zapier - Publishing content and fetching posts

Other Questions Zapier
1

I’m trying to work with LinkedIn’s REST API through Zapier’s webhook functionality. The main reason I’m using Zapier is to avoid dealing with OAuth tokens myself.

My Goals:

  1. Get my personal LinkedIn posts from my profile
  2. Create new posts with text and images

Issue with retrieving posts:
I’m sending a GET request to https://api.linkedin.com/rest/posts with these parameters:

  • Header: LinkedIn-Version: 202408
  • Query param: author=urn:li:person:USER_ID

But I keep getting “No virtual resource found” error.

Issue with creating posts:
For POST requests to the same endpoint, I’m using this JSON payload:

{
  "author": "urn:li:person:USER_ID",
  "commentary": "Sample post content",
  "visibility": "PUBLIC",
  "lifecycleState": "PUBLISHED",
  "distribution": {
    "feedDistribution": "MAIN_FEED",
    "targetEntities": [],
    "thirdPartyDistributionChannels": []
  }
}

Same error occurs here too.

Interestingly, when I test https://api.linkedin.com/rest/me, it works perfectly and returns my profile data, so authentication seems fine.

I’m not a registered LinkedIn developer, just a regular user trying to automate posting. Could this be a permissions issue? Any ideas what I might be missing?

2

The “No virtual resource found” error typically indicates that you’re trying to access an API endpoint that requires specific permissions or developer access. Given that you aren’t a registered LinkedIn developer, this is likely your main issue. Regular LinkedIn users generally don’t have access to the Posts API endpoints without being approved through LinkedIn’s Developer Program. You’ll need to create a LinkedIn app and obtain permissions such as r_liteprofile and w_member_social to post content.

I faced a similar roadblock when attempting to automate LinkedIn posts for my company. I assumed Zapier would simplify the process, but LinkedIn’s restrictions still apply, even with third-party tools handling OAuth. Your best course of action would be to register as a developer to get the appropriate API access, or alternatively, consider using LinkedIn’s native scheduling tools for basic posting needs.

3

Yeah, LinkedIn’s API is a pain - they’ve locked down most useful features unless you’re enterprise. Zapier handles OAuth fine, but can’t give you permissions LinkedIn doesn’t want regular users to have. Even registered developers struggle getting posts API approval now. LinkedIn pushes their paid tools instead. Check if Zapier has pre-built LinkedIn integrations that bypass the raw API calls.

4

You’re hitting LinkedIn’s API restrictions - they’ve gotten really strict over the years. The Posts API endpoint needs specific approval from LinkedIn, even through Zapier. Since /rest/me works but /rest/posts doesn’t, that confirms it - basic profile stuff is way more accessible than posting features. I ran into this exact issue building automation workflows. LinkedIn killed most of their open APIs and now makes businesses go through their Marketing Developer Platform for posting. Even if you register as a developer, getting post permissions can take weeks and you need to prove legitimate business use. For personal automation, try LinkedIn’s native integrations or maybe browser automation tools, though those risk ToS violations.

5

Had this same problem last year - LinkedIn’s API permissions are a nightmare.

You need developer approval AND business verification for the Posts API. Zapier can’t get around those restrictions either.

I fixed it with Latenode using browser automation instead of their API. It acts like a real user, so no special permissions required. You can schedule posts, add images, and analyze existing content.

The visual workflow builder is dead simple. Set triggers, connect your content sources, automate everything. Works with other platforms too without hitting API limits.

Beats waiting forever for LinkedIn’s developer approval that might never happen.