LinkedIn Mentionables

List the LinkedIn members you can @mention — a per-user directory of people whose native member ids Publora has captured from engagement on your connected company pages. Each entry includes a ready-to-paste mention token for create-post content, comment messages, or reshare commentary.

Why this exists: person mentions require LinkedIn's native member id (e.g. Dk968RHxiO), which cannot be derived from a linkedin.com profile URL. This directory is where Publora surfaces every native id it has seen for you. See the LinkedIn Mentions Guide for the full id explanation and name-matching rules.

Paid plans only. Free plans receive a 403 UPGRADE_REQUIRED error (see Errors).

List Mentionable People

GET https://api.publora.com/api/v1/linkedin-mentionables

Headers

Query Parameters

Results are sorted by lastSeenAt descending — the most recently engaged people first.

Response (HTTP 200)

{
  "success": true,
  "people": [
    {
      "personId": "Dk968RHxiO",
      "name": "Daria Bulaeva",
      "profileUrl": "",
      "profilePicture": "",
      "source": "comment",
      "lastSeenAt": "2026-07-16T10:00:00.000Z",
      "mention": "@{urn:li:person:Dk968RHxiO|Daria Bulaeva}"
    }
  ]
}

Note: The mention token uses the person's full captured name. LinkedIn matches display names strictly — if you edit the name part, follow the name matching rules (first name, last name, or full name; exact case; nothing extra).

Examples

JavaScript (fetch)

const params = new URLSearchParams({ q: 'daria', limit: '10' });
const response = await fetch(
  `https://api.publora.com/api/v1/linkedin-mentionables?${params}`,
  { headers: { 'x-publora-key': 'YOUR_API_KEY' } }
);
const data = await response.json();
 
for (const person of data.people) {
  if (person.mention) {
    console.log(`${person.name}: ${person.mention}`);
  }
}

cURL

curl "https://api.publora.com/api/v1/linkedin-mentionables?q=daria&limit=10" \
  -H "x-publora-key: YOUR_API_KEY"

How the Directory Fills

The directory is populated automatically — there is no endpoint to add people manually:

• When comments or reactions are read on posts of your connected company pages (via the Publora app's engagement views or the feed-retrieval API), LinkedIn returns each engaging member's native app-scoped person id, and Publora persists it in your directory.
• No extra LinkedIn API calls are made — the ids are captured as a side effect of reads you already perform.
• Engagement on personal-profile posts is not capturable — LinkedIn restricts the required scope. Only company-page engagement feeds the directory.
• Placeholder/unresolved actors (entries LinkedIn returns without a resolvable member) are skipped.

There is no way to add an arbitrary person by profile URL — the ACoAA… web-profile ids visible on linkedin.com cannot be converted to native ids. See Finding LinkedIn URNs for the full explanation of native vs web-profile ids.

MCP Tool

The same directory is available to MCP clients as the linkedin_list_mentionables tool, with the same q/limit parameters and the same paid-plan requirement. See the MCP Tools Reference.

Errors

Note: API keys already require a paid plan, so API callers normally hit the 403 API-access error before the UPGRADE_REQUIRED one; the latter mainly appears in edge cases (e.g. a plan downgrade with a still-active key).

Related

• LinkedIn Mentions Guide — mention syntax, native vs web-profile ids, name matching
• LinkedIn Comments — mention people in comments
• LinkedIn Reshare — mention people in reshare commentary
• Create Post — mention people in scheduled posts

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.