---
title: "Resolve LinkedIn mention"
method: GET
path: "/v1/accounts/{accountId}/linkedin-mentions"
tags: ["LinkedIn Mentions"]
---

# Resolve LinkedIn mention

`GET /v1/accounts/{accountId}/linkedin-mentions`

Converts a LinkedIn profile or company URL to a URN for @mentions in posts.

How to use LinkedIn @mentions (2-step workflow):

1. Call this endpoint with the LinkedIn profile/company URL to get the mention URN and format.
2. Embed the returned mentionFormat (e.g. @[Vincent Jong](urn:li:person:xxx)) directly in your post's content field.

Example:
- Resolve: GET /v1/accounts/{id}/linkedin-mentions?url=linkedin.com/in/vincentjong&displayName=Vincent Jong
- Returns: mentionFormat: "@[Vincent Jong](urn:li:person:xxx)"
- Use in post content: "Great talk with @[Vincent Jong](urn:li:person:xxx) today!"

Important: The mentions array field in POST /v1/posts is stored for reference only and does NOT trigger @mentions on LinkedIn. You must embed the mention format directly in the content text.

Requirements:
- Person mentions require the LinkedIn account to be admin of at least one organization. This is a LinkedIn API limitation: the only endpoints that resolve profile URLs to member URNs (vanityUrl, peopleTypeahead) are scoped to organization followers. There is no public LinkedIn API to resolve a vanity URL without organization context.
- Organization mentions (e.g. @Microsoft) work without this requirement.
- For person mentions to be clickable, the displayName parameter must exactly match the name shown on their LinkedIn profile.
- Person mentions DO work when published from personal profiles (the URN just needs to be valid). The limitation is only in the resolution step (URL to URN), not in publishing.

## Path parameters

- `accountId` string, required

## Query parameters

- `url` string, required
- `displayName` string

## Response `200`

URN resolved successfully

- object
  - `urn` string — The LinkedIn URN (person or organization)
  - `type` 'person' | 'organization' — The type of entity (person or organization)
  - `displayName` string — Display name (provided, from API, or derived from vanity URL)
  - `mentionFormat` string — Ready-to-use mention format for post content
  - `vanityName` string — The vanity name/slug (only for organization mentions)
  - `warning` string — Warning about clickable mentions (only present for person mentions if displayName was not provided)

## Other responses

- `400` — Invalid request or no organization found (for person mentions)
- `401` — Unauthorized
- `403` — The account holds no organization role that can resolve person mentions
- `404` — Person or organization not found

---

[API](https://skmtc.net/zernio/apis/zernio-api.md) · [All operations](https://skmtc.net/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zernio/zernio-api/revisions/15e893e69e8c/schema)
