late-sdk 0.0.114 → 0.0.115
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.
- checksums.yaml +4 -4
- data/docs/LinkedInMentionsApi.md +1 -1
- data/lib/late-sdk/api/linked_in_mentions_api.rb +2 -2
- data/lib/late-sdk/version.rb +1 -1
- data/openapi.yaml +3 -2
- data/spec/api/linked_in_mentions_api_spec.rb +1 -1
- data/zernio-sdk-0.0.115.gem +0 -0
- metadata +3 -3
- data/zernio-sdk-0.0.114.gem +0 -0
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d231226f0971b82bf81a610a30c19132fbe96dd25f2a2f573bc3ab38785f28b7
|
|
4
|
+
data.tar.gz: 93d355c6c5ee273802b3a0552848314e245bcf6949e172608ec5b77d29cc8091
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cce1fadb9dc362c721bebe987b1e09e65d8f1d6248dad2e529bcae530246b87951cf35243b97ebc78115150cf7ccd1777a3d8b520240626011af5b306e6eb1f5
|
|
7
|
+
data.tar.gz: 3159e70f56c237417a30d28fb5a0818182a4deb2c01dd51647689ef0edbf428c68957f8b4c2a52ca889776222a5c93de15284cbdab12880571c6e1ed6626c976
|
data/docs/LinkedInMentionsApi.md
CHANGED
|
@@ -13,7 +13,7 @@ All URIs are relative to *https://zernio.com/api*
|
|
|
13
13
|
|
|
14
14
|
Resolve LinkedIn mention
|
|
15
15
|
|
|
16
|
-
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. - 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.
|
|
16
|
+
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.
|
|
17
17
|
|
|
18
18
|
### Examples
|
|
19
19
|
|
|
@@ -20,7 +20,7 @@ module Late
|
|
|
20
20
|
@api_client = api_client
|
|
21
21
|
end
|
|
22
22
|
# Resolve LinkedIn mention
|
|
23
|
-
# 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. - 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.
|
|
23
|
+
# 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.
|
|
24
24
|
# @param account_id [String] The LinkedIn account ID
|
|
25
25
|
# @param url [String] LinkedIn profile URL, company URL, or vanity name.
|
|
26
26
|
# @param [Hash] opts the optional parameters
|
|
@@ -32,7 +32,7 @@ module Late
|
|
|
32
32
|
end
|
|
33
33
|
|
|
34
34
|
# Resolve LinkedIn mention
|
|
35
|
-
# 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. - 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.
|
|
35
|
+
# 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.
|
|
36
36
|
# @param account_id [String] The LinkedIn account ID
|
|
37
37
|
# @param url [String] LinkedIn profile URL, company URL, or vanity name.
|
|
38
38
|
# @param [Hash] opts the optional parameters
|
data/lib/late-sdk/version.rb
CHANGED
data/openapi.yaml
CHANGED
|
@@ -10023,9 +10023,10 @@ paths:
|
|
|
10023
10023
|
**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.
|
|
10024
10024
|
|
|
10025
10025
|
**Requirements:**
|
|
10026
|
-
- Person mentions require the LinkedIn account to be admin of at least one organization.
|
|
10027
|
-
- Organization mentions (e.g. @Microsoft) work without this requirement.
|
|
10026
|
+
- **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.
|
|
10027
|
+
- **Organization mentions** (e.g. @Microsoft) work without this requirement.
|
|
10028
10028
|
- For person mentions to be clickable, the `displayName` parameter must exactly match the name shown on their LinkedIn profile.
|
|
10029
|
+
- 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.
|
|
10029
10030
|
parameters:
|
|
10030
10031
|
- name: accountId
|
|
10031
10032
|
in: path
|
|
@@ -34,7 +34,7 @@ describe 'LinkedInMentionsApi' do
|
|
|
34
34
|
|
|
35
35
|
# unit tests for get_linked_in_mentions
|
|
36
36
|
# Resolve LinkedIn mention
|
|
37
|
-
# 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. - 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.
|
|
37
|
+
# 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.
|
|
38
38
|
# @param account_id The LinkedIn account ID
|
|
39
39
|
# @param url LinkedIn profile URL, company URL, or vanity name.
|
|
40
40
|
# @param [Hash] opts the optional parameters
|
|
Binary file
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: late-sdk
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.115
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- OpenAPI-Generator
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-04-
|
|
11
|
+
date: 2026-04-07 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: typhoeus
|
|
@@ -2439,7 +2439,7 @@ files:
|
|
|
2439
2439
|
- spec/models/you_tube_scope_missing_response_scope_status_spec.rb
|
|
2440
2440
|
- spec/models/you_tube_scope_missing_response_spec.rb
|
|
2441
2441
|
- spec/spec_helper.rb
|
|
2442
|
-
- zernio-sdk-0.0.
|
|
2442
|
+
- zernio-sdk-0.0.115.gem
|
|
2443
2443
|
homepage: https://openapi-generator.tech
|
|
2444
2444
|
licenses:
|
|
2445
2445
|
- Unlicense
|
data/zernio-sdk-0.0.114.gem
DELETED
|
Binary file
|