In this PostCast episode Omar and myself figure out how to save the LinkedIn API token. Previously we saved the LinkedIn API ClientID and ClientSecret, which we knew was incorrect, but we just wanted to get something working. Now we correctly save the token, which is what should be saved.
*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.
[Read More]In this episode Omar and myself hook up the Post to LinkedIn button and prompt the user to enter the credentials for LinkedIn, and it all works. Not the best flow, but we are still in the proof of concept stage.
We also learn about Go structs and how you can attach methods to them so get something similar to an object in other languages.
*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.
[Read More]We get a Proof of Concept (PoC) in Go that completes the LinkedIn authorization. We end up figuring out the difference between a LinkedIn code and token. Get a code by entering your LinkedIn username and password, then use that code to get a token. We also spin up a local webserver to deal with the callback which is required to enter credentials and get the code.
*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.
[Read More]Turns out getting a LinkedIn API key is confusing, at least for us. Did you know you need an Organization Page on @LinkedIn to get a key? You can’t just get an API key for yourself. No actual coding in this video, just lots of reading the LinkedIn docs and getting some curl scripts to work. If you have any tips for using LinkedIn API, let us know in the comments.
[Read More]