Resolve LinkedIn mention
Converts a LinkedIn profile or company URL to a URN for @mentions in posts.
How to use LinkedIn @mentions (2-step workflow):
- Call this endpoint with the LinkedIn profile/company URL to get the mention URN and format.
- Embed the returned mentionFormat (e.g. @Vincent Jong) 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"
- Use in post content: "Great talk with @Vincent Jong 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: both endpoints that resolve a profile URL to a member URN take an organization you administer. Organization mentions (e.g. @Microsoft) have no such requirement.
- The two are not scoped alike. peopleTypeahead?q=organizationFollowers only returns that organization's followers; vanityUrl?q=vanityUrlAsOrganization does not, and its resolvable set is opaque. A 404 here does not mean the person is unknown to you or unknown to LinkedIn: a live public profile can 404 with no reason given.
- 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 only needs to be valid). The limitation is only in the resolution step (URL to URN), not in publishing.
Billing: Read (free unless it says otherwise) · Rate limit: 120/min
Request
- Base URL: https://apihub.co.il
- URL: https://apihub.co.il/v1/messaging/accounts/{accountId}/linkedin-mentions
- Auth: HTTP bearer
Path parameters
The LinkedIn account ID
Query parameters
LinkedIn profile URL, company URL, or vanity name.
Exact display name as shown on LinkedIn. Required for person mentions to be clickable. Optional for org mentions.
Headers
Replay-safe: the same execution is returned instead of charging twice
Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…
Response
Completed
Changes
No recorded changes to this operation across all 2 revisions of this API.