Week 4

Apr 05, 2021

Hello everyone, I hope you’ve all had a fantastic weekend!

This past week, I continued developing my backend listening agent which pulls data every time my intern company, Federated Wireless, is mentioned on social media. As a recap, I previously applied for and was granted developer access to Twitter and promptly developed code that allowed my program to pull tweets and other data from the platform. Now, after being granted developer access to Facebook, I’ve finished developing the code needed to pull data related to Federated Wireless on Facebook.

This week was quite difficult actually. This is largely due to the fact that making HTTP requests to Facebook proved to be extra cumbersome as there are a lot more authentications required between each request compared to Twitter. Not because Facebook is more “secure” than Twitter per say, but because they use different authentication requirements for different API calls. If that last sentence made no sense to you then let me break it down. When a programmer is given developer access to an API, they are given 5 strings of text. They’re given an access key, an access key secret, an API key, an API key secret, and a bearer token. Both Twitter and Facebook use the same authentication standard (OAuth 2.0 for those that are interested). So, when making calls to Twitter’s API, I only needed to provide a bearer token to identify myself. However, when making calls to Facebook’s API, I needed to provide different authentication strings for different calls.

In the end, despite these challenges, I still managed to successfully develop code that can interact with Facebook’s API. This week, I’ll be developing code that makes calls to LinkedIn’s API.

That’s all for now. Have a great Monday!

One Reply to “Week 4”

  1. Aaron Glanzer says:

    Interesting that both websites use such different authentication requirements. Good handle of an unexpected challenge! Let’s hope LinkedIn doesn’t have too many different restrictions.

Leave a Reply