LinkedIn Reshare

Reshare (repost) an existing LinkedIn post to your own feed, with optional commentary. Works for both personal profile and company page connections.

There are two ways to repost on LinkedIn via Publora:

1. Immediate reshare — POST /linkedin-reshare (this page). The repost is published right away.
2. Scheduled reshare — set platformSettings.linkedin.repostParentUrn on create-post / update-post. The repost goes through the normal scheduling pipeline (see Scheduled Reshares below).

Reshare a Post

POST https://api.publora.com/api/v1/linkedin-reshare

Headers

Request Body

Note: The reshare is authored automatically as the correct entity for the connection — urn:li:person:* for a personal profile, urn:li:organization:* for a company page. You do not pass the author yourself.

Mentions in commentary: Person mentions must use LinkedIn's native member id (e.g. Dk968RHxiO), not the ACoAA… web-profile ids from linkedin.com URLs — those are rejected with a 400 error. See the LinkedIn Mentions Guide for where to find native ids and the name-matching rules.

Response (HTTP 201 Created)

{
  "success": true,
  "reshare": {
    "lifecycleState": "PUBLISHED",
    "id": "urn:li:share:7123456789012345678"
  }
}

Note: Creating a reshare returns HTTP 201, not 200. The reshare.id is the URN of the newly created reshare post (read from LinkedIn's x-restli-id response header); the rest of the reshare object is the LinkedIn API response body.

Examples

JavaScript (fetch)

const response = await fetch('https://api.publora.com/api/v1/linkedin-reshare', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-publora-key': 'YOUR_API_KEY'
  },
  body: JSON.stringify({
    platformId: 'linkedin-Tz9W5i6ZYG',
    parent: 'urn:li:share:7123456789012345678',
    commentary: 'Great read — sharing with my network!',
    visibility: 'PUBLIC'
  })
});
const data = await response.json();
console.log(data.reshare.id); // urn:li:share:...

Python (requests)

import requests
 
response = requests.post(
    'https://api.publora.com/api/v1/linkedin-reshare',
    headers={
        'Content-Type': 'application/json',
        'x-publora-key': 'YOUR_API_KEY'
    },
    json={
        'platformId': 'linkedin-Tz9W5i6ZYG',
        'parent': 'urn:li:share:7123456789012345678',
        'commentary': 'Great read — sharing with my network!'
    }
)
print(response.json()['reshare']['id'])

cURL

curl -X POST https://api.publora.com/api/v1/linkedin-reshare \
  -H "Content-Type: application/json" \
  -H "x-publora-key: YOUR_API_KEY" \
  -d '{
    "platformId": "linkedin-Tz9W5i6ZYG",
    "parent": "urn:li:share:7123456789012345678",
    "commentary": "Great read — sharing with my network!",
    "visibility": "PUBLIC"
  }'

Node.js (axios)

const axios = require('axios');
 
await axios.post(
  'https://api.publora.com/api/v1/linkedin-reshare',
  {
    platformId: 'linkedin-Tz9W5i6ZYG',
    parent: 'urn:li:ugcPost:7123456789012345678'
  },
  { headers: { 'x-publora-key': 'YOUR_API_KEY' } }
);

parent Format

Use urn:li:share:xxx or urn:li:ugcPost:xxx — not urn:li:activity:xxx.

The urn:li:activity: URN is what appears in LinkedIn post URLs (e.g. linkedin.com/feed/update/urn:li:activity:123), but it is rejected by this endpoint with a 400 error.

To get the correct URN:

• For posts created via Publora, use the postedId field from the get-post response
• The activity ID and share ID are typically the same number — try replacing urn:li:activity: with urn:li:share: (e.g. urn:li:activity:7451373349668282369 → urn:li:share:7451373349668282369)

Errors

Note: The error response for a failed LinkedIn call includes a details string with the underlying LinkedIn error message: { "error": "Failed to create LinkedIn reshare", "details": "<LinkedIn error message>" } (unlike the reactions endpoint, there is no separate status field in the body).

Note: Error status codes from the LinkedIn API may be forwarded directly (e.g., 403 if the post's author disabled resharing, 429 on rate limits), so you may receive error codes other than those listed above.

Scheduled Reshares

To schedule a repost for a future time instead of publishing immediately, use the normal scheduling pipeline with LinkedIn platform settings:

const response = await fetch('https://api.publora.com/api/v1/create-post', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-publora-key': 'YOUR_API_KEY'
  },
  body: JSON.stringify({
    content: 'My commentary on this great post.',
    platforms: ['linkedin-Tz9W5i6ZYG'],
    scheduledTime: '2026-08-01T14:00:00.000Z',
    platformSettings: {
      linkedin: {
        repostParentUrn: 'urn:li:share:7123456789012345678',
        repostVisibility: 'PUBLIC'
      }
    }
  })
});

The post content becomes the reshare commentary. Media is not allowed on repost groups. See Create Post → LinkedIn Repost Settings for the full field reference and validation rules.

Publora is built by Creative Content Crafts, Inc. Need AI-powered content creation for LinkedIn, Threads, and X? Try Co.Actor — the best AI service for authentic thought leadership at scale.