Power Platform Community Forum Thread Details

Hi Community,

I’m experiencing a persistent 422 error ("author field is required but not found and has no default value") when testing a custom connector in Power Apps for the LinkedIn API endpoint https://api.linkedin.com/rest/posts. Despite following the exact setup provided by the LinkedIn Support Team, which worked successfully via curl, the connector fails to send the request body, resulting in this validation error. This is blocking my ability to post content programmatically.

Details:

- Endpoint: https://api.linkedin.com/rest/posts
- Method: POST
- Headers: Bearer {access_token} (using OAuth 2.0 with w_member_social scope, set up as advised earlier)
- Body:

{
"author": "urn:li:person:6pAAJRl4XN",
"commentary": "Test post from Power Apps",
"visibility": "PUBLIC",
"distribution": {
"feedDistribution": "MAIN_FEED",
"targetEntities": [],
"thirdPartyDistributionChannels": []
},
"lifecycleState": "PUBLISHED",
"isReshareDisabledByAuthor": false
}

Under New Policy Tab I created HTTP Headers for

- LinkedIn-Version: 202501
- Content-Type: application/json (implied by body)

Why because under Import from Sample tab we don't have extra headers.

Error Response:

- Status: 422
- Body: {"message": "ERROR :: /author :: field is required but not found and has no default value\n", "status": 422}
- Test Logs: The connector sends an empty or missing body, as seen in the test tab (logs attached).
- Contrast with Success: The LinkedIn Support Team confirmed this setup works with their curl command (attached reference), suggesting the issue lies with the Power Apps connector.

Please find the attachment screen shot of error status 422 for reference.

Note: The LinkedIn Support Team ran the same test and successfully posted in my LinkedIn account without issues. Please assist me in resolving this problem.

Regards,

Sathya Sai.

Categories:

Connector development