@zernio/node 0.2.42 → 0.2.43
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/generated/sdk.gen.ts +3 -2
package/package.json
CHANGED
package/src/generated/sdk.gen.ts
CHANGED
|
@@ -1145,9 +1145,10 @@ export const updateLinkedInOrganization = <ThrowOnError extends boolean = false>
|
|
|
1145
1145
|
* **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.
|
|
1146
1146
|
*
|
|
1147
1147
|
* **Requirements:**
|
|
1148
|
-
* - Person mentions require the LinkedIn account to be admin of at least one organization.
|
|
1149
|
-
* - Organization mentions (e.g. @Microsoft) work without this requirement.
|
|
1148
|
+
* - **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.
|
|
1149
|
+
* - **Organization mentions** (e.g. @Microsoft) work without this requirement.
|
|
1150
1150
|
* - For person mentions to be clickable, the `displayName` parameter must exactly match the name shown on their LinkedIn profile.
|
|
1151
|
+
* - 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.
|
|
1151
1152
|
*
|
|
1152
1153
|
*/
|
|
1153
1154
|
export const getLinkedInMentions = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetLinkedInMentionsData, ThrowOnError>) => {
|