<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ana Gonçalves on Medium]]></title>
        <description><![CDATA[Stories by Ana Gonçalves on Medium]]></description>
        <link>https://medium.com/@sbg_ana?source=rss-256a7e3ac5bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_ZCdH2y9PuMvXpUb.jpeg</url>
            <title>Stories by Ana Gonçalves on Medium</title>
            <link>https://medium.com/@sbg_ana?source=rss-256a7e3ac5bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:48:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sbg_ana/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Integrating a Third Party API with Rails 5]]></title>
            <link>https://medium.com/runtime-revolution/integrating-a-third-party-api-with-rails-5-134f960ddbba?source=rss-256a7e3ac5bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/134f960ddbba</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[rails-5]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ana Gonçalves]]></dc:creator>
            <pubDate>Thu, 24 Aug 2017 10:53:04 GMT</pubDate>
            <atom:updated>2017-08-24T10:53:04.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVHo2zmRuVRN7BBp4HTD_A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/52gEprMkp7M?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dennis Kummer</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Sometimes you have an idea for an application but don’t want the hassle of collecting the data you need, or perhaps you need a service to complement your existing app. Whatever reason it might be, sometimes you just need to integrate a third party API. I will show you a quick and easy example on how to use an API to populate the app with some useful data. Let’s get to it!</p><h3>Setup the API</h3><p>I really like cooking so I decided to build a recipe app for this. I will be using the <a href="https://spoonacular.com/">Spoonacular</a> API which is available through <a href="https://www.mashape.com/">Mashape</a>. The API documentation is available at this <a href="https://market.mashape.com/spoonacular/recipe-food-nutrition">link</a>. In order to setup the API, we will need the API token that’s given to our mashape’s account.</p><p>After creating our app, we need to add some gems to the Gemfile. We need <a href="https://github.com/bkeepers/dotenv">dotenv-rails</a>, to keep the API token as an environment variable, and <a href="https://github.com/lostisland/faraday">faraday</a> to make requests to Spoonacular API.</p><pre>gem &#39;dotenv-rails&#39;<br>gem &#39;faraday&#39;</pre><p>In order to establish the connection and make requests to the third party API, I have created two classes, <em>Connection</em> and <em>Request,</em> under <em>lib/spoonacular</em> folder. This is a fairly simple code for now. Here is what they look like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/548705093cb3a51512e8b488206a2af2/href">https://medium.com/media/548705093cb3a51512e8b488206a2af2/href</a></iframe><p>In the <em>Connection</em> class, I added the API base URL and the configuration necessary to create a Faraday connection with our base URL and API token.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a6d6da4ba3efebc4edcf551253eece8/href">https://medium.com/media/5a6d6da4ba3efebc4edcf551253eece8/href</a></iframe><p>The <em>Request</em> class will then be responsible for making the actual requests to Spoonacular API. At this point, we’re ready to create the classes we need to populate our app with some recipes.</p><h3>Processing Data</h3><p>We now have what we need to make requests to the Spoonacular API. After studying the API, we can design the class structure for the data that we need to represent. This application will only list a few recipes and show their details. So, in this case, we have recipes and a recipe has multiple ingredients and instructions.</p><p>For starters, let’s create a <em>Spoonacular::Base</em> class with an attribute <em>errors</em> and the initialization method that’s common to all the spoonacular classes we will create. I recommend that all classes be created under <em>app/services/spoonacular </em>folder, but the organization is up to you<em>.</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/55d664a43951d1d4884af7f4b3f2990e/href">https://medium.com/media/55d664a43951d1d4884af7f4b3f2990e/href</a></iframe><p>After checking the Spoonacular API once again, we will need two specific endpoints, one for the recipes list and another one for the recipe details:</p><pre>GET recipes/random<br>GET recipes/:id/information</pre><p>As you are no doubt expecting, we will now create the <em>Spoonacular::Recipe</em> class which, as previously mentioned, inherits from <em>Spoonacular::Base.</em> This class will have <em>random</em> and <em>find</em> methods that will use <em>Request</em> class to make these two requests. We will also need to override the initialization method, in order to parse the ingredients and instructions that come in the HTTP response.</p><p>Let’s take a look at the code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c27417378ce7b7f3a266154badffc06/href">https://medium.com/media/6c27417378ce7b7f3a266154badffc06/href</a></iframe><p>As you can see, for each recipe that comes in the response a <em>Spoonacular::Recipe</em> object is created. Also several <em>Spoonacular::Ingredient</em> and <em>Spoonacular::Instruction</em> objects are created and kept in the recipe attributes. The code for these last two classes is pretty straightforward, since we just want to store the data.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/597ad647bce2e083b6d7f9597e08eae1/href">https://medium.com/media/597ad647bce2e083b6d7f9597e08eae1/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/26393e167ec2ee3c1bcacf29cda75ad8/href">https://medium.com/media/26393e167ec2ee3c1bcacf29cda75ad8/href</a></iframe><p>Note: we’re not covering requests other than <em>GET,</em> but take a look at <a href="https://github.com/lostisland/faraday">Faraday</a> documentation for more information.</p><h3>Building the Application</h3><p>We’re ready to build our interface. As mentioned before, this interface will have the recipes list and the recipe details. Therefore, it should not be hard to guess that we need to implement <em>index</em> and <em>show</em> for <em>RecipesController:</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/98ad4df50164917c51dff3a5a53dc968/href">https://medium.com/media/98ad4df50164917c51dff3a5a53dc968/href</a></iframe><p>I kept the page layout and styling pretty simple, basically added a few options to the menu and some icons to visually categorize the recipes. Since it is not the scope of this article, I’ll not cover the markup and styling, but you can take a look at the final result <a href="https://github.com/AnnieLee/blog-spoonacular-api">here</a>. (Note: if you want to run the application, you’ll have to add the <em>.env</em> file with the mashape key)</p><p>In case you’re interested in organizing your CSS and you’re missing some tips, at Runtime Revolution we have an article that covers that. You can check it out in the link below. In this tutorial, for example, I’m using <a href="https://suitcss.github.io/">SUIT CSS</a> as a naming convention.</p><p><a href="https://revs.runtime-revolution.com/organize-your-css-with-bem-4a680fe5ced6">Organize Your CSS with BEM</a></p><p>Here’s what the application looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ONUQd10atdjbKQAZr2cIFw.png" /><figcaption>Home Page</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RFq9m9KESsujDUgEmQGurA.png" /><figcaption>Recipe Page</figcaption></figure><h3>Adding Cache</h3><p>In some cases you might be interested in adding cache to your API requests. Mashaple does have a pricing table that limits the request quota per month, but sometimes you might want to improve the application response time. Either way, there’s multiple reasons to justify adding cache to our system. In this case, we want to avoid unnecessary requests to Spoonacular API, since it can become pricier.</p><p>Looking at the final result of the application, I can think of two ways of minimizing the number of requests made. The obvious one is the recipe information endpoint. Once we have the recipe data, it will not change frequently, so we can assume that we won’t need to request this endpoint every time the recipe page is accessed.</p><p>I’m also thinking about adding a refresh button on the home page. This way we can cache the recipes list and clean it up whenever the user wants to.</p><p>We will then have to make some changes to the method <em>get_json</em> from <em>Request</em> class. Using <a href="http://api.rubyonrails.org/classes/ActiveSupport/Cache/Store.html"><em>ActiveSupport::Cache::Store</em></a> we can store the requests response using the endpoint as key. See the example below:</p><pre>Rails.cache.fetch(&quot;recipes/random&quot;, expires_in: 7.days, force: false) do<br>   /* make request */<br>end</pre><p>Here’s the changes to <em>request.rb</em>, <em>recipe.rb</em> and <em>recipes_controller.rb:</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9137474011e68b6ab24a798f6830045f/href">https://medium.com/media/9137474011e68b6ab24a798f6830045f/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/42afdfe7d790f411f11664b1d457a7b1/href">https://medium.com/media/42afdfe7d790f411f11664b1d457a7b1/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a12c77a4818535c8c2304ae9cff9de08/href">https://medium.com/media/a12c77a4818535c8c2304ae9cff9de08/href</a></iframe><h3>Testing</h3><p>I did not add tests to the code base, but it is good practice to add a couple of them. In case you’re interested in learning about tests around third party APIs, we have a couple of articles that cover this subject. Check them out:</p><ul><li><a href="https://revs.runtime-revolution.com/a-simple-trick-to-make-your-classes-easier-to-test-d27b42b67715">A simple trick to make your classes easier to test</a></li><li><a href="https://revs.runtime-revolution.com/unit-testing-with-vcr-5dd2bb5c9012">Unit testing with VCR</a></li></ul><p>That will be all folks. Obviously this is a really simple example, but I think it is enough to get the gist of it. I hope this will help you to get started and work on awesome stuff!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*kKg0eJWVGNXhMYQQjsfVdw.gif" /><figcaption>Have a nice day!</figcaption></figure><h3>Recommended links</h3><p>Summary of recommended links throughout the article and some more:</p><ol><li><a href="https://www.mashape.com/">Mashape</a></li><li><a href="https://market.mashape.com/spoonacular/recipe-food-nutrition">Spoonacular API</a></li><li><a href="https://github.com/lostisland/faraday">Faraday</a></li><li><a href="https://revs.runtime-revolution.com/a-simple-trick-to-make-your-classes-easier-to-test-d27b42b67715">A simple trick to make your classes easier to test</a></li><li><a href="https://revs.runtime-revolution.com/unit-testing-with-vcr-5dd2bb5c9012">Unit testing with VCR</a></li><li><a href="https://revs.runtime-revolution.com/organize-your-css-with-bem-4a680fe5ced6">Organize Your CSS with BEM</a></li><li><a href="https://suitcss.github.io/">SUIT CSS</a></li></ol><p><a href="https://github.com/AnnieLee/blog-spoonacular-api">AnnieLee/blog-spoonacular-api</a></p><p><em>If you have any comments, questions or suggestions, I’d love to hear them. Let me know if you found this article useful, or if you have any tips on working with third party APIs.</em></p><p><em>I am currently working at </em><a href="http://www.runtime-revolution.com/"><em>Runtime Revolution</em></a><em>. We are a team of developers that work from sunny Lisbon to everywhere. We focus on delivering and maintaining the best possible products to our clients, while having fun, learning and helping each other.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=134f960ddbba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/runtime-revolution/integrating-a-third-party-api-with-rails-5-134f960ddbba">Integrating a Third Party API with Rails 5</a> was originally published in <a href="https://medium.com/runtime-revolution">Runtime Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with Facebook using Devise, Omniauth, Koala and Rails 5]]></title>
            <link>https://medium.com/runtime-revolution/working-with-facebook-using-devise-omniauth-koala-and-rails-5-cde5d032de02?source=rss-256a7e3ac5bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cde5d032de02</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[social]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Ana Gonçalves]]></dc:creator>
            <pubDate>Thu, 01 Jun 2017 08:30:24 GMT</pubDate>
            <atom:updated>2017-06-01T08:30:24.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rv5w_FHeWWhrU65QLG4Isw.png" /></figure><p>The feature that possibly every developer had to implement at some point in their career is user authentication. In some cases, you might want to make use of Facebook accounts to facilitate the login/authentication process. That’s why I will guide you through a simple Rails 5 application that works with Facebook using <a href="https://github.com/plataformatec/devise">devise</a>, <a href="https://github.com/arsduo/koala">OmniAuth Facebook</a> and <a href="https://github.com/arsduo/koala">Koala</a>. So let’s begin!</p><h3>Facebook App</h3><p>First of all, we need to setup our Facebook app. There’s not much to add on this, simply create a new Facebook app if needed. When your app is created, make sure to add the proper app domain. In this case, the app domain will be <em>localhost</em> to allow us to test it locally, but it should be changed to work properly on your staging or production environment. Also, make sure to add a platform according to what kind of application you’re working on. Here I selected a website and the site URL should match the app domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*ulfLcnpadwfc0K0yESAohA.png" /><figcaption>Facebook App settings page</figcaption></figure><h3>Setting up the Rails app</h3><p>As I mentioned, we will be using <a href="https://github.com/plataformatec/devise">devise</a>, <a href="https://github.com/mkdynamic/omniauth-facebook">OmniAuth Facebook</a> and <a href="https://github.com/arsduo/koala">Koala</a>. So after creating the new Rails 5 app, the next step should be adding these gems to our gemfile:</p><pre>gem &#39;devise&#39;<br>gem &#39;omniauth-facebook&#39;<br>gem &#39;koala&#39;</pre><p>Next, we will need the User model. We will add <em>uid</em> and <em>token</em> for Facebook and we will not add email as devise will do that for us.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7a5e29b186a648cf48e28415185f1bbd/href">https://medium.com/media/7a5e29b186a648cf48e28415185f1bbd/href</a></iframe><p>After creating the User model, don’t forget to setup devise:</p><pre>rake db:migrate<br>rails generate devise:install<br>rails generate devise User</pre><p>Next, we will add our Facebook app keys in <em>config/initializers/devise.rb</em>:</p><pre>config.omniauth :facebook,<br>                ENV[&quot;FB_APP_ID&quot;],<br>                ENV[&quot;FB_APP_SECRET&quot;],<br>                scope: &#39;email,user_likes&#39;</pre><p>In this case, I set up a .env file with the Facebook keys using the gem <a href="https://github.com/bkeepers/dotenv">dotenv</a>. I also added the scope of our app. In this example, this will ask permission to allow our app to access the user’s email and likes. Since we are only interested in using devise with omniauth, this is what we should add to <em>user.rb</em> to setup devise:</p><pre>devise :omniauthable, :omniauth_providers =&gt; [:facebook]</pre><p>We also need a <em>callbacks_controller</em> to process the Facebook authentication callback. I added mine in a controllers/auth folder, but you can add it anywhere you want as long as you describe it in your routes file:</p><pre>devise_for :users, controllers: { omniauth_callbacks: &#39;auth/callbacks&#39; }</pre><p>At this point, we are ready to start our application.</p><h3>Building the App</h3><p>The application we will be building will allow the user to login using a Facebook account. Then we will be using the user’s access token to get the list of books and movies that the user likes.</p><p>For starters, I created a homepage with a login button that leads us to a Facebook dialog. This Facebook dialog will then ask the user permission to access his information through our app.</p><p>To link the login button to Facebook, omniauth provides a route called <em>user_facebook_omniauth_authorize. </em>After the user gives consents to our app’s permissions, we will need to handle the response using our <em>callbacks_controller</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*ZMwotM_kP3lnAjtEJiBrGQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*eKERZNTKHJrip_WipBuLhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*R4kGS-YhnPoxFlsK0sYX4A.png" /><figcaption>Login screen — Facebook dialog — User homepage</figcaption></figure><p>Let’s take a look at the code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/51a6f5ffa7717996612d87683f9881e4/href">https://medium.com/media/51a6f5ffa7717996612d87683f9881e4/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/200f988c0faddc9d732b5029d70751ec/href">https://medium.com/media/200f988c0faddc9d732b5029d70751ec/href</a></iframe><p>As you can see, the <em>callbacks_controller</em> has two actions: <em>facebook</em> and <em>failure</em>. These names should be self-explanatory and our focus will be on the <em>facebook</em> action. In here we can access the user’s account information with request.env[&quot;omniauth.auth&quot;] and we will use it to create a user if needed.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9463db08c4090cf76046aedec5484907/href">https://medium.com/media/9463db08c4090cf76046aedec5484907/href</a></iframe><p>At this stage, the user can successfully login in our application. The information we have access to through the Facebook app allows us to create a new user and proceed with the authentication. Note that I added some simple styling and templates to the application, though I won’t be addressing those in this post. You can take a look at the <a href="https://github.com/AnnieLee/blog-facebook">end result</a> if you want.</p><p>Now that we have the authentication working, we will work on getting the books and movies list. Remember that we kept the user’s Facebook token? This is where it is needed since the token is required to work with Facebook Graph API.</p><p>We will now be working with Koala, and for this I like to have a separate class to handle the Facebook requests. In this example, we only need the <em>get_object</em> method, but Koala provides a lot more <a href="http://www.rubydoc.info/github/arsduo/koala/Koala/Facebook/GraphAPIMethods">methods</a> that we could use, I recommend you check it out.</p><p>Let’s take another look at the code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/de96a95634d0bed632db76cc9bb7e876/href">https://medium.com/media/de96a95634d0bed632db76cc9bb7e876/href</a></iframe><p>Next, we will be using the Facebook service to fetch the data we need. In this example, we will be fetching books and movies, but we could be doing a lot more. I recommend taking some time to look at the <a href="https://developers.facebook.com/docs/graph-api/reference">Graph API documentation</a> or playing around with <a href="https://developers.facebook.com/tools/explorer/">Graph API Explorer</a>. These are great to have a sense of what the Graph API has to offer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cce4e49da84b8e14bdfd728315835c95/href">https://medium.com/media/cce4e49da84b8e14bdfd728315835c95/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0cc78f3f8a7042f60461b1999e3642a3/href">https://medium.com/media/0cc78f3f8a7042f60461b1999e3642a3/href</a></iframe><p>In this case, the list is showing name, picture, and author/studio. In order to do that, we need to specify the fields we want in the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*A4e88XtMcm6VY-g-E_SNfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*jUuT47zrKTJA5kP2Z-BmVA.png" /><figcaption>Books List — Movies List</figcaption></figure><p>So that pretty much sums it! This is a simple example of how to work with Facebook, from authentication to fetching data. I hope this will help you to get started and work on awesome stuff!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*uVT_Z2Z9gg9Gv6YY3_ohsw.gif" /></figure><h3>Recommended links</h3><p>Summary of recommended links throughout the article and some more:</p><ol><li><a href="https://developers.facebook.com/docs/graph-api">Graph API Documentation</a></li><li><a href="https://developers.facebook.com/tools/explorer/">Graph API Explorer</a></li><li><a href="http://www.rubydoc.info/github/arsduo/koala/Koala/Facebook/GraphAPIMethods">Koala Graph API methods</a></li><li><a href="https://github.com/arsduo/koala/wiki/Graph-API">Koala &amp; Graph API examples</a></li><li><a href="https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview">Devise &amp; Omniauth Overview</a></li><li><a href="https://github.com/mkdynamic/omniauth-facebook#configuring">OmniAuth Facebook Configuration options</a></li></ol><p><a href="https://github.com/AnnieLee/blog-facebook">AnnieLee/blog-facebook</a></p><p><em>If you have any comments, questions or suggestions, I’d love to hear them. Let me know if you found this article useful, or if you have any tips on working with Facebook or any of these gems.</em></p><p><em>I am currently working at </em><a href="http://www.runtime-revolution.com/"><em>Runtime Revolution</em></a><em>. We are a team of developers that work from sunny Lisbon to everywhere. We focus on delivering and maintaining the best possible products to our clients, while having fun, learning and helping each other.</em></p><p><a href="http://www.runtime-revolution.com/">Runtime Revolution</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cde5d032de02" width="1" height="1" alt=""><hr><p><a href="https://medium.com/runtime-revolution/working-with-facebook-using-devise-omniauth-koala-and-rails-5-cde5d032de02">Working with Facebook using Devise, Omniauth, Koala and Rails 5</a> was originally published in <a href="https://medium.com/runtime-revolution">Runtime Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>