Skip to content

Commit

Permalink
reduce main summary
Browse files Browse the repository at this point in the history
  • Loading branch information
drmowinckels committed Jan 14, 2025
1 parent 00330f7 commit a0c6be8
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions content/blog/2025/02-01_linkedin-api/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,7 @@ tags:
slug: "linkedin-api"
image: featured.png
image_alt: "A professional digital illustration featuring a confident woman, with a polished appearance. She has medium-length dark hair styled neatly, wearing a business-casual outfit, consisting of a tailored blazer and a soft-colored blouse. The background is a gradient of neutral tones, giving a modern, LinkedIn-style look, with a faint abstract design that suggests professionalism and a digital context."
summary: "I share my experience integrating R with the LinkedIn API, focusing on personal authentication and posting processes. The documentation and workflow were complex, but with help from the rOpenSci community, I successfully navigated the challenges. I detail steps for API access, authentication, and creating posts, highlighting key obstacles like managing OAuth tokens, API products, and endpoints.
My approach, blending contributions from Steffi LaZerte and Jon Harmon, simplifies API usage and includes reusable R code for future projects. This post reflects months of learning, aiming to guide others in overcoming similar hurdles."
summary: "I share my experience integrating R with the LinkedIn API, focusing on personal authentication and posting processes. The documentation and workflow were complex, but with help from the rOpenSci community, I successfully navigated the challenges. I detail steps for API access, authentication, and creating posts, highlighting key obstacles like managing OAuth tokens, API products, and endpoints."
seo: "Master LinkedIn API in R with my detailed guide on authentication, posting, and overcoming documentation challenges."
---

Expand Down

0 comments on commit a0c6be8

Please sign in to comment.