<?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 David Noah on Medium]]></title>
        <description><![CDATA[Stories by David Noah on Medium]]></description>
        <link>https://medium.com/@david_13998?source=rss-94d94b1711d1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Dtyg1rYfoONalyIY.</url>
            <title>Stories by David Noah on Medium</title>
            <link>https://medium.com/@david_13998?source=rss-94d94b1711d1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:29:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@david_13998/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[The Basetrip: The Ultimate Traveling API]]></title>
            <link>https://medium.com/@david_13998/the-basetrip-the-ultimate-traveling-api-6340ec1443e0?source=rss-94d94b1711d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6340ec1443e0</guid>
            <dc:creator><![CDATA[David Noah]]></dc:creator>
            <pubDate>Thu, 29 Jun 2017 17:28:49 GMT</pubDate>
            <atom:updated>2017-06-29T17:28:54.983Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m always down to travel. Whether it’s eating mango sticky rice in Vietnam, swimming with sharks in Australia, or rock climbing in California, sign me up!</p><p><a href="https://giphy.com/gifs/party-warning-davin-MOTkF7sT8u2Z2">via GIPHY</a></p><p>That’s why I was so excited when I found the Basetrip API. There are a good amount of travel APIs out there, including <a href="https://rapidapi.com/category/Travel%20&amp;%20Transportation?utm_source=Blog&amp;utm_medium=BasetripProfile_FlightAPIs&amp;utm_content=Blog">a number of flight APIs</a>. But the Basetrip API is the first I’ve found that provides local data specific to travelers (ex. electrical socket types).</p><p>Read on for…</p><ul><li>An overview of the Basetrip API</li><li>A tutorial for a script that finds upcoming flights to a destination (via Google Flights API) and pairs that response with in-depth local travel information (via the Basetrip API)</li></ul><h4><strong>The Basetrip API Overview</strong></h4><p>The Basetrip API accesses travel information for over 230 countries. The response includes helpful travel information like…</p><ul><li>Tipping customs</li><li>Internet speeds</li><li>Currencies and credit card types accepted</li><li>Local alcohol laws</li></ul><p>…and more. You can check out the <a href="https://www.thebasetrip.com/en/api/docs">Basetrip documentation here</a> to learn more about what the API provides. A lot of the more intricate details can be unlocked by subscribing to a Pro, Ultra, or Mega plan. But don’t worry, the API is free when you subscribe to its Basic tier and make requests within the limit. You can find more details about the Basetrip <a href="https://rapidapi.com/user/the-basetrip/package/The%20Basetrip/pricing?utm_source=Blog&amp;utm_medium=BasetripProfile_BasetripPricing&amp;utm_content=Blog">pricing plans on RapidAPI</a>.</p><h4><strong>Connecting to the Basetrip API</strong></h4><p>Now that you understand what kind of information you can access with the Basetrip API, let’s test some API calls.</p><p><strong>Step 1: Create a RapidAPI account<br> <br> </strong>In order to connect to the Basetrip API, you’ll first need to create a RapidAPI account. Head to the <a href="http://rapidapi.com/?utm_source=Blog&amp;utm_medium=BasetripProfile_homepage&amp;utm_content=Blog">homepage</a> and click “Login” to sign up for an account.</p><p><strong>Step 2: Subscribe to the Basetrip API</strong></p><p>Once you have created an account, navigate to the <a href="https://rapidapi.com/user/the-basetrip/package/The%20Basetrip/pricing?utm_source=Blog&amp;utm_medium=BasetripProfile_BasetripPricing&amp;utm_content=Blog">Basetrip API pricing page</a> to subscribe to a plan.</p><p>Here, you will see four different pricing tiers. Each tier will unlock extra features and allow for a higher volume of requests to be made. For the scope of this tutorial, we only need to subscribe to the <strong>Basic Plan. </strong>This will allow us to test the API and build this API smash without spending money. Go ahead and click “Choose Plan” under the Basic tier. A modal should pop up asking for your credit card information.</p><p>Fill in your credit card information and click “checkout”. You will not be charged anything unless you exceed the maximum amount of monthly requests (in this case 1,000 requests).</p><p><strong>Step 3: Make a test call</strong></p><p>While you can call the API manually, a great way to test out an API is to use the RapidAPI tool within the browser. Navigate to the <a href="https://rapidapi.com/user/the-basetrip/package/The%20Basetrip/functions?utm_source=Blog&amp;utm_medium=BasetripProfile_BasetripFunctions&amp;utm_content=Blog">Basetrip API functions page</a>. If you’re logged in, you should see that your X-Mashape-Key is already filled in — it’s generated when you initially create a RapidAPI account (RapidAPI and Mashape are part of <a href="https://goo.gl/utlfuv">one larger API marketplace</a>). Testing the API is as easy as clicking TEST Function. You should see a JSON response on the right. Above the response, you can also export the API call in numerous different languages. Here is an example of the NodeJS code snippet:</p><p>In order to use this Unirest API call in a project, you must install the Unirest client. Simply follow the instructions on the <a href="http://unirest.io/nodejs.html">Unirest website</a>.</p><h4><strong>API Smash: Google Flights and the Basetrip API</strong></h4><p>Travel information is helpful, but let’s be real, flight prices can make or break a trip. We built a script for more effective adventure-planning. This project pairs Google Flights’ upcoming flights (and prices!) with the Basetrip API information for a more complete picture. Here’s how we did it.</p><h4><strong>Connecting to the Google Flights API</strong></h4><p>Now that we have fully connected to the Basetrip API, we must also connect to the Google Flights API. Connecting to the Google Flights API is a slightly different process. You do not need a subscription to connect to the API, but you do need to retrieve an API key from Google.</p><p><strong>Step 1: Get a Google Flights API key</strong></p><ol><li>Go to the <a href="https://console.developers.google.com/apis/dashboard?project=box-era&amp;authuser=1&amp;duration=PT1H">Google Developers Console</a></li><li>Log in with your google account or create a new account</li><li>Select a project, or create a new one</li><li>Go to the <a href="https://console.developers.google.com/apis/api/qpxexpress-json.googleapis.com/overview">QRX Express Airfare API Dashboard</a> on Google’s API Manager (Google acquired this API, so the name of the API isn’t “Google Flights API”)</li><li>Click the “Enable” button towards the top of the page</li><li>Go to the credentials tab on the left side of Google’s API manager to get your apiKey</li></ol><p><strong>Step 2: Make a test call</strong></p><p>Using your shiny new apiKey, you can call the API at the <a href="https://rapidapi.com/package/GoogleFlightsAPI/functions?utm_source=Blog&amp;utm_medium=BasetripProfile_GoogleFlightsFunctions&amp;utm_content=Blog">Google Flights API functions page</a>. Just pick an endpoint, then fill in the required parameters, including your apiKey.</p><p>Once you test out the API just like you did for the Basetrip API, you can again export the API call as a code snippet in the language of your choice. Check out our <a href="https://docs.rapidapi.com/docs/nodejs">SDK docs</a> to find out how to use/install RapidAPI for each language.</p><h4><strong>Combining both APIs to Implement the API Smash</strong></h4><p>Now that you’ve connected to both the Basetrip API and the Google Flight API within the browser, let’s combine them into one script that returns data from both about your destination!</p><p>The script we have created is written in Node, but you can use any language you prefer.</p><pre>const RapidAPI = require(&#39;rapidapi-connect&#39;);<br><br>const rapid = new RapidAPI(&quot;****&quot;, &quot;***************************&quot;);<br><br>const unirest = require(&#39;unirest&#39;);<br><br><br><br>// Get both destination arguments<br><br>let destinationFrom = process.argv[2];<br><br>let destinationTo = process.argv[3];<br><br><br><br>// Call Google Flights API first, passing two IATA city codes<br><br>rapid.call(&#39;GoogleFlightsAPI&#39;, &#39;searchSingleTrip&#39;, {<br><br>&#39;apiKey&#39;: &#39;*************************&#39;,<br><br>&#39;origin&#39;: destinationFrom,<br><br>&#39;destination&#39;: destinationTo,<br><br>&#39;passengersAdultCount&#39;: &#39;1&#39;,<br><br>&#39;passengersChildCount&#39;: &#39;0&#39;,<br><br>&#39;fromDate&#39;: &#39;2017-06-20&#39;<br><br><br><br>}).on(&#39;success&#39;, (googleFlightsPayload) =&gt; {<br><br><br><br>// convert IATA destination city code to country code<br><br> rapid.call(&#39;IATACodes&#39;, &#39;getCitiesByCodes&#39;, {<br><br>  &#39;apiKey&#39;: &#39;**********************&#39;,<br><br>  &#39;cityCodes&#39;: `${destinationTo}`<br><br><br><br> }).on(&#39;success&#39;, (destToCity) =&gt; {<br><br><br><br>// convert IATA country code to country name<br><br> rapid.call(&#39;IATACodes&#39;, &#39;getCountriesByCodes&#39;, {<br><br>   &#39;apiKey&#39;: &#39;***********************&#39;,<br><br>   &#39;countryCodes&#39;: `${destToCity[0].response[0].country_code}`<br><br><br><br>   }).on(&#39;success&#39;, (destToCountry) =&gt; {<br><br><br><br>// call the Basetrip API passing in the country name into the URL<br><br>     unirest.get(`https://thebasetrip.p.mashape.com/v2/countries/${destToCountry[0].response[0].name}`)<br><br>       .header(&quot;X-Mashape-Key&quot;, &quot;*****************************&quot;)<br><br>         .header(&quot;Content-Type&quot;, &quot;application/json&quot;)<br><br>           .header(&quot;Accept&quot;, &quot;application/json&quot;)<br><br>             .end((result) =&gt; {<br><br><br><br>// Log the Basetrip and GoogleFlights data<br><br>               console.log(result.body, googleFlightsPayload);<br><br>             });<br><br>   }).on(&#39;error&#39;, (err) =&gt; {<br><br>      throw err;<br><br>   });<br><br> }).on(&#39;error&#39;, (err) =&gt; {<br><br>  throw err;<br><br> });<br><br>}).on(&#39;error&#39;, (err) =&gt; {<br><br>  throw err;<br><br>});</pre><p>The script returns data from both the GoogleFlights API and the Basetrip API. To run the script, you must also include two arguments: the departure city and the destination city. Try running something similar to this in your terminal: ‘node [filePath] BOS PAR’ and see what kind of data you get back! Don’t forget, if you’re using the code from above, you need to add all the required API keys.</p><p>You’ll notice that I also included the <a href="https://rapidapi.com/package/IATACodes/functions?utm_source=Blog&amp;utm_medium=BasetripProfile_IATACodesFunctions&amp;utm_content=Blog">IATACodes API</a> in this script. Further proof that there is an API for everything! I found that the Google Flights API takes in IATA city codes as parameters, but the Basetrip API requires one to use full country names. Two calls to the IATA API will provide this conversion. Connecting to the IATACodes API is as easy as signing up <a href="http://iatacodes.org/">here</a> and using the API key generated for you.</p><h4>Conclusion<strong></strong></h4><p>Time to stop reading and start packing! Let us know what you think of the Basetrip API and feel free to <a href="https://github.com/RapidAPI/Basetrip-GoogleFlights-Smash">clone the repo</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6340ec1443e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mail Overdue Invoices with this Lob Integration [Rails Tutorial]]]></title>
            <link>https://medium.com/@david_13998/mail-overdue-invoices-with-this-lob-integration-rails-tutorial-ac6805b5c2e7?source=rss-94d94b1711d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac6805b5c2e7</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[rails]]></category>
            <dc:creator><![CDATA[David Noah]]></dc:creator>
            <pubDate>Thu, 16 Mar 2017 16:45:23 GMT</pubDate>
            <atom:updated>2017-03-16T18:33:46.272Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mail Invoices Programmatically Using APIs [Rails Tutorial]</h3><figure><img alt="screen-shot-2017-03-14-at-4-55-47-pm" src="https://cdn-images-1.medium.com/max/296/0*Pfx4X4fgGXmqV4Fz.png" /></figure><p>Emailed invoices are easy to ignore. But a physical letter? Mailed invoices can earn higher response rates — especially for overdue payments. One brand study <a href="https://www.linkedin.com/pulse/20140625042138-19675079-case-study-direct-mail-vs-email-invoices">reported</a> that <strong>the majority (59%) of its customers failed to pay on first billing when emailed</strong> and needed additional reminders. Yikes. On the other hand, <strong>only 29%</strong> of those billed by direct mail failed to pay on first billing and required follow-up.</p><p>In this tutorial, we will build a simple Rails app that acquires all invoices associated with your invoicing system and gives you the option to send the invoices by mail programmatically using <a href="http://www.lob.com/">the Lob API</a>. Read on for the full tutorial or skip ahead to <a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration">GitHub code</a>.</p><h3><strong>SETTING UP</strong></h3><p>This tutorial is written primarily for Rails, but the concepts can be translated across languages.</p><h4><strong>What you’ll need</strong></h4><ul><li>A free <a href="https://rapidapi.com/?utm_source=Medium&amp;utm_medium=LobFreshbooks_home">RapidAPI</a> account to test API calls and export code snippets</li><li>A <a href="http://lob.com/">Lob</a> account to send the physical mail</li><li>An invoicing system (we’ll use <a href="https://www.freshbooks.com/">Freshbooks</a>’ free 30 day trial)</li></ul><h4><strong>What you’ll build</strong></h4><p>We’ll build this project in Rails and define two routes: get_invoices, and send_invoice. Using ERB and the <a href="https://github.com/lob/lob-templates/blob/master/letters/invoice/invoice.html">Lob invoice template</a>, we will dynamically generate an invoice with all of the Freshbooks invoice details filled out. We will call the Freshbooks and Lob APIs using <a href="https://rapidapi.com/?utm_source=Medium&amp;utm_medium=LobFreshbooks_home">RapidAPI</a>. RapidAPI allows us to test the API calls in our browser and see a JSON response. It will also export the API call as a code snippet in the language of your choice.</p><h4><strong>What the final project will do</strong></h4><p>This tutorial will walk through how to programmatically send an invoice from Freshbooks via the US Postal Service with Lob. Note, we won’t be covering how to build a frontend.</p><p>When the app is visited, all of your Freshbooks’ invoices will rendered in a list along with a Send Mail button. When you click the Send Mail button, ERB will dynamically generate an invoice with all of the invoice information.</p><figure><img alt="lobgif" src="https://cdn-images-1.medium.com/max/480/0*7FADFPqip8NONbao.gif" /></figure><p>The resulting invoice document will look something like this, but you can customize it as you see fit.</p><figure><img alt="screen-shot-2017-02-08-at-4-35-50-pm" src="https://cdn-images-1.medium.com/max/817/0*MYucb8ff94IRQHd7.png" /></figure><p>Finally, the app will send the invoice through the United States Postal Service via Lob’s API. Pretty cool, right?</p><h3><strong>BUILDING THE PROJECT</strong></h3><p>Let’s walk through the steps to build this application. If you reach a roadblock, you can compare your code to the <strong>finished project in</strong><a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration"><strong> this repo.</strong></a></p><h3><strong>Step 1: Create an invoice controller</strong></h3><p>Before we mail the invoices out, we’ll need to retrieve them! The invoice controller will send all the invoices to the frontend and populate the app. Since we’re using <a href="http://freshbooks.com/">Freshbooks</a> as our invoicing system (thank you, 30 day free trial!), we’ll call our controller the Freshbooks controller. Here are the steps we took:</p><blockquote>1. Make a Freshbooks account</blockquote><p>1a. Travel to <a href="https://my.freshbooks.com/#/signup">https://my.freshbooks.com/#/signup</a> and create an account.</p><p>1b. Populate a new business with invoices or import your existing business invoices. We chose to make Dave’s Construction business because, hey, who wouldn’t want to build stuff all day?</p><blockquote>2. Call the Freshbooks API getInvoices endpoint on RapidAPI</blockquote><p>2a. The first thing you will need to do is generate an access token. Head to <a href="https://rapidoauth.com/freshbooks">https://rapidoauth.com/freshbooks</a></p><p>2b. After you generate the access token, you’ll be taken directly into the RapidAPI testing environment. Test out your new access token with the getIdentityInfo endpoint!</p><p>2c. Look through the JSON response and find your Freshbooks accountID. (response -&gt; roles -&gt; accountId). Copy this ID onto your clipboard.</p><figure><img alt="freshbooksid" src="https://cdn-images-1.medium.com/max/480/0*G03YF6dsgRMW8q_L.gif" /></figure><p>2d. Go to the <a href="https://rapidapi.com/package/FreshbooksAPI/functions/getInvoices?utm_source=Medium&amp;utm_medium=LobFreshbooks_FreshbooksgetInvoices">getInvoices endpoint</a>. Enter your access token and paste your account ID. Expand the optional parameters section and add the word “lines” to the “include” parameter. This addition will give us access to all the details about each item on an invoice.</p><p>2e. Click the TEST Function button to call the API! <br> <br> 2f. Sign in to generate a code snippet in Ruby. You can call an API without a RapidAPI account, but you’ll need one to access the code snippet.</p><blockquote><em>3. Build a custom route and controller</em></blockquote><p>3a. Start a new Rails project (rails new [project_name]) or navigate to an existing project.</p><p>3b. Type rails g controller freshbooks into your terminal.</p><p>3c. Define a custom route ( get &#39;freshbooks/get_invoices&#39;, :to =&gt; &#39;freshbooks#get_invoices&#39;) in your config/routes.rb file.</p><p>3d. Write gem &#39;rapidapi&#39;, &#39;~&gt; 0.1.3&#39; in your Gemfile. Then, run bundle install in Terminal.</p><p>3e. In your FreshbooksController, define a method called get_invoices and copy and paste your RapidAPI getInvoices code snippet that was saved from the previous step.</p><blockquote>Note: Prefix each RapidAPI class with a double colon “::”. These colons tell Rails to not implicitly call ‘self’ before calling the RapidAPI class.</blockquote><p>3f. Finally, write render json: JSON.pretty_generate(root[‘payload’][‘response’][‘result’][‘invoices’]) as the last line in your controller.</p><p>3g. Start your server with rails s and navigate to localhost:3000/freshbooks/get_invoices. You should see a JSON response of all the invoices within your Freshbooks account.</p><blockquote><strong>Ta-da! You’re done with the invoice controller.</strong></blockquote><p>Your invoice controller should look like this:</p><pre>def get_invoices<br><br>   require &#39;rapidapisdk&#39;<br><br>   ::RapidAPI.config(project: &quot;LobFreshbooks&quot;, token: ‘############’)<br><br>   root = ::RapidAPI.call(&#39;FreshbooksAPI&#39;, &#39;getInvoices&#39;, {<br><br>    &#39;accessToken&#39;: &#39;###################&#39;,<br><br>    &#39;accountId&#39;: &#39;#####&#39;,<br><br>      &#39;include&#39;: &#39;lines&#39;<br><br>   })<br><br>   render json: JSON.pretty_generate(root[&#39;payload&#39;][&#39;response&#39;][&#39;result&#39;][&#39;invoices&#39;])<br><br>end</pre><h3><strong>Step 2: Make a Lob Controller</strong></h3><p>Now that the invoicing controller is all set, we can move onto the Lob controller. The Lob controller will actually call the Lob API and send the invoice as a physical piece of mail (or a virtual one if we’re in test mode). Let’s build it!</p><p>Since this process is slightly more complicated than the invoice controller, we’ve divided it into three sections: <strong>set up, connect to RapidAPI, generate invoice.</strong></p><h4><strong>A) Set up your Lob account and Lob controller</strong></h4><p>To kick this process off, we’ll create a Lob account and skeleton Lob controller.</p><blockquote>1.<em>Create a Lob account and get your Test API Key</em></blockquote><p>1a. Head to Lob to sign up for an API key: <a href="https://dashboard.lob.com/#/settings/keys">https://dashboard.lob.com/#/settings/keys</a></p><p>1b. Copy the “Test API Key” onto your clipboard.</p><figure><img alt="lob-key-14-gif" src="https://cdn-images-1.medium.com/max/480/0*Ii6Pr-Ozvb-Bmmtx.gif" /></figure><p><em>Why are we using the test API key? This key allows us to make calls and test them without sending out physical mail just yet. Another bonus? We won’t be charged for calls using a test API key.</em></p><blockquote><em>2. Set up your Lob controller</em></blockquote><p>2a. Run rails g controller Lob in Terminal.</p><p>2b. Create another custom route in your routes.rb file to look like get &#39;lob/send_invoice&#39;, :to =&gt; &#39;lob#send_invoice&#39;.</p><p>2c. Define a method in your LobController called send_invoice.</p><h4><strong>B) Connect your Lob controller to the Lob API with RapidAPI</strong></h4><p>Here’s where it gets interesting…We will be sending our Freshbooks invoice details along with our AJAX call to the send_invoice route.</p><blockquote><em>1. Connect to RapidAPI to call Lob’s createLetter endpoint</em></blockquote><p>1a. This step should feel familiar! Go to the <a href="https://rapidapi.com/package/Lob/functions/createLetter?utm_source=Medium&amp;utm_medium=LobFreshbooks_LobCreateLetter">createLetter endpoint on RapidAPI’s Lob package</a>. Paste your Lob “Test API Key” into the apiKey form.</p><p>1b. Test the API call and see the JSON results. Generate the code snippet in Ruby. Copy and paste this code snippet directly into your send_invoice method.</p><blockquote>Note: Again, prefix each RapidAPI class with a double colon “::”.</blockquote><blockquote><em>2. Fill out the API parameters</em></blockquote><p>2a. Create letterTo and letterFrom address objects. The letterTo and letterFrom parameters in your Lob RapidAPI call take a JSON address object that looks like this:</p><pre>‘letterTo’: JSON.generate({<br><br>name: params[&#39;name&#39;],<br><br>        address_line1: params[&#39;address_line_1&#39;],<br><br>        address_city: params[&#39;city&#39;],<br><br>        address_state: Lob.state[params[&#39;state&#39;].to_sym],<br><br>        address_country: Lob.iso[params[&#39;country&#39;]],<br><br>        address_zip: params[&#39;zip_code&#39;]<br><br>})</pre><p>Notice that each line of the letterTo address object contains an invoice parameter.</p><p>2b. Next, implement state and country conversions. Why do we need these? The Freshbooks JSON response returns full country and state names (ie. “California” or “India”) but the Lob API takes state and country abbreviations. <br> <br> Since the address_country and address_state parameters access a Lob model, we’ll need to generate a new Lob model (rails g model Lob). Take a look at <a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration/blob/master/app/models/lob.rb">our Lob model</a> to see how we built it and see the two country and state hash objects. Then, implement the two state and country hash objects into two methods respectively.</p><p>2c. Fill in the letterFrom parameter with your company’s information:</p><pre>&#39;letterFrom&#39;: JSON.generate({<br><br>        name: &quot;Dave&#39;s Construction&quot;,<br><br>        address_line1: &quot;600 California St.&quot;,<br><br>       address_city: &#39;San Francisco&#39;,<br><br>        address_state: &#39;CA&#39;,<br><br>       address_country: &#39;US&#39;,<br><br>        address_zip: &#39;94109&#39;<br><br>     })</pre><h4><strong>C) Generate an invoice programmatically within your Lob controller</strong></h4><p>Finally, we’ll use ERB to generate an invoice within the Lob controller.</p><blockquote><em>1. Create an .erb file</em></blockquote><p>1a. If Rails hasn’t already created a lob/send_invoice.html.erb within your views folder, go ahead and do so now.</p><p>1b. Navigate to <a href="https://github.com/lob/lob-templates/blob/master/letters/invoice/invoice.html">Lob’s invoice template </a>and copy Lob’s invoice template into the send_invoice.html.erb file that you just created.</p><blockquote><em>2. Alter the file to generate the invoice based on Freshbooks params</em></blockquote><p>2a. Access to the @params variable we defined in our LobController in the .erb file. <a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration/blob/master/app/views/lob/send_invoice.html.erb">Check out our finished .erb file here</a> to get an idea of how you should modify this file.</p><blockquote><em>3. Modify send_invoices method in LobController to generate the .erb file</em></blockquote><p>3a. Bind the @params variable to the .erb file to generate its result using this code snippet.</p><p>3b. Add these four lines to your code above the RapidAPI.call function</p><pre>@params = params<br><br>  Dir.chdir(File.dirname(__FILE__))<br><br>  erb_string = File.read(&#39;../views/lob/send_invoice.html.erb&#39;)<br><br>  renderer = ERB.new(erb_string)<br><br>  result = renderer.result(binding)</pre><p>The first line just ensures that our master directory is set as our current directory, then we read our .erb file. Once we have read our .erb file we need to create a new instance of the ERB class, pass our .erb file as an argument, and render the result. The “binding” key word is Rails’ way of passing all of our needed variables (in this case, the instance variable @params) to our template.</p><p>3c. Our RapidAPI.call method takes a file parameter. Go ahead and set the variable “result” as our file. The final line of your send_invoice method should say render json: response.</p><blockquote><strong>Boom! You’ve got your Lob Controller.</strong></blockquote><p>Once your are finished, your LobController#send_invoice method should look similar to this:</p><pre>def send_invoice<br><br>   require &#39;rapidapisdk&#39;<br><br>   ::RapidAPI.config(project: [YourRapidProject], token: [YourRapidProjectKey])<br><br>   @params = params<br><br>   <br><br>   Dir.chdir(File.dirname(__FILE__))<br><br>   erb_string = File.read(&#39;../views/lob/send_invoice.html.erb&#39;)<br><br>   renderer = ERB.new(erb_string)<br><br>   result = renderer.result(binding)<br><br>   response = ::RapidAPI.call(&#39;Lob&#39;, &#39;createLetter&#39;, {<br><br>    &#39;apiKey&#39;: &#39;###########################&#39;,<br><br>    &#39;letterTo&#39;: JSON.generate({<br><br>        name: params[&#39;name&#39;],<br><br>        address_line1: params[&#39;address_line_1&#39;],<br><br>        address_city: params[&#39;city&#39;],<br><br>        address_state: Lob.state[params[&#39;state&#39;].to_sym],<br><br>        address_country: Lob.iso[params[&#39;country&#39;]],<br><br>        address_zip: params[&#39;zip_code&#39;]<br><br>      }),<br><br>    &#39;letterFrom&#39;: JSON.generate({<br><br>        name: &quot;Dave&#39;s Construction&quot;,<br><br>        address_line1: &quot;600 California St.&quot;,<br><br>        address_city: &#39;San Francisco&#39;,<br><br>        address_state: &#39;CA&#39;,<br><br>       address_country: &#39;US&#39;,<br><br>        address_zip: &#39;94109&#39;<br><br>     }),<br><br>    &#39;color&#39;: true,<br><br>    &#39;file&#39;: result<br><br>   })<br><br>   render json: response<br><br> end</pre><h4><strong>Step 3: Build a Frontend</strong></h4><p>We won’t go into too much detail about how your frontend should look, but just know that you should have two AJAX calls: one to the freshbooks/get_invoices route, and another to your lob/send_invoice route. This project populates the frontend with invoices on the initial loading of the app and displays buttons for each invoice to send by mail respectively. The frontend uses React.js. Feel free to use <a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration/tree/master/frontend">our sample frontend</a> as a way to get this app up and running.</p><pre>get_invoices:<br><br>$.get({<br><br>    url: &#39;freshbooks/get_invoices&#39;<br><br>  });<br><br>send_invoice:<br><br>$.get({<br><br>      url: &#39;lob/send_invoice&#39;,<br><br>      data: {<br><br>        name: invoice.fname + &quot; &quot; + invoice.lname,<br><br>        amount: invoice.amount,<br><br>        organization: invoice.organization,<br><br>        address_line_1: invoice.street,<br><br>        city: invoice.city,<br><br>        state: invoice.province,<br><br>        zip_code: invoice.code,<br><br>        country: invoice.country,<br><br>        invoice_number: invoice.invoice_number,<br><br>        customer_id: invoice.customerid,<br><br>        create_date: invoice.create_date,<br><br>        lines: invoice.lines<br><br>     }<br><br>}).done(function(res) {<br><br>      console.log(res);<br><br>   });</pre><h4><strong>Conclusion</strong></h4><p>While this tutorial focuses on Freshbooks, you can replicate the project with any invoicing system. RapidAPI has <a href="https://rapidapi.com/package/Shopify/functions?utm_source=Medium&amp;utm_medium=LobFreshbooks_ShopifyFunctions">Shopify</a>, <a href="https://rapidapi.com/package/SquareECommerce/functions?utm_source=Blog&amp;utm_medium=LobFreshbooks_SquareEcommFunctions">SquareEcommerce</a> and <a href="https://rapidapi.com/package/Stripe/functions?utm_source=Medium&amp;utm_medium=LobFreshbooks_StripeFunctions">Stripe</a>, or you could call the APIs directly.</p><p>Let us know what you build and feel free to raise an issue on <a href="https://github.com/RapidSoftwareSolutions/LobFreshbooksIntegration">GitHub</a> with any questions or concerns. Happy invoicing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6805b5c2e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build an Alexa Flight Departure Skill [TUTORIAL]]]></title>
            <link>https://medium.com/@david_13998/weve-all-been-there-1bb7e60c6aaf?source=rss-94d94b1711d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bb7e60c6aaf</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[amazon]]></category>
            <dc:creator><![CDATA[David Noah]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 22:25:47 GMT</pubDate>
            <atom:updated>2017-02-07T22:39:32.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/497/0*vmOtQRPhMF727rZA.gif" /></figure><p>We’ve all been there. You *think* your flight is on time. But sure enough, by the time you get to the airport, you find that it’s been delayed for hours.</p><figure><img alt="Source: GIPHY " src="https://cdn-images-1.medium.com/max/355/0*LDPgPEl094l0yBga." /><figcaption>Source: <a href="http://giphy.com/gifs/shirley-bennett-Ho1mzZUO2tA40">GIPHY</a></figcaption></figure><p>What if you could ask Alexa about your flight status before heading out the door? We built a skill that connects Alexa to the <a href="https://rapidapi.com/package/LaminarFlightData/functions?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_LaminarFunctionsAPI">Laminar Flight API</a> so that you can ask Alexa the status of your flight. Even better? We created a video tutorial that walks you through every step of the process. Check out the video tutorial below or visit <a href="https://github.com/RapidAPI/LaminarAPI-AlexaSkill?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_AlexaLaminarGitHub"><strong>our GitHub</strong></a> to see the code.</p><h4><strong>This video tutorial will go through…</strong></h4><ol><li>Adding the departure time skill to Amazon Alexa</li><li>Creating the skill’s backend in AWS Lambda</li><li>Connecting Alexa to the <a href="https://rapidapi.com/package/LaminarFlightData/functions?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_LaminarFunctionsAPI">Laminar Flight API</a> using RapidAPI</li></ol><h4><strong>The result</strong></h4><p>The end result will look something like this…</p><figure><img alt="alexalaminar-gif" src="https://cdn-images-1.medium.com/max/497/0*bjQ92WT62hC6Ijjb.gif" /></figure><h4><strong>What you’ll need:</strong></h4><ul><li>Amazon Echo device</li><li>Amazon account</li></ul><p>Let the hacking begin! Watch the tutorial below, follow along on <a href="https://github.com/RapidAPI/LaminarAPI-AlexaSkill?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_AlexaLaminarGitHub">GitHub</a> and feel free to leave any questions in the comments.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FN_H6m2dJ6fo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DN_H6m2dJ6fo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FN_H6m2dJ6fo%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/214b9f91e2d0662173f0512339badfc4/href">https://medium.com/media/214b9f91e2d0662173f0512339badfc4/href</a></iframe><h4><strong>Feeling inspired?</strong></h4><p>One Alexa skill is never enough. Here are other project ideas that you could build by connecting to RapidAPI:</p><ul><li>Use the <a href="https://rapidapi.com/package/Twilio/functions?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_TwilioFunctions">Twilio API</a> or the <a href="https://rapidapi.com/package/Plivo/functions?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_PlivoFunctions">Plivo API</a> to have Alexa send a text message</li><li>Build a Google Translate Skill with <a href="http://blog.rapidapi.com/2016/10/07/alexa-api-project/?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_AlexaGoogleTranslatePost">this written tutorial</a></li><li>Recommend local events with the <a href="https://rapidapi.com/package/EventbriteAPI/functions?utm_source=Medium&amp;utm_medium=AlexaLaminarTutorial_EventbriteFunctions">Eventbrite API</a> or the <a href="https://rapidapi.com/package/Meetup/functions">Meetup API</a></li></ul><p>Let us know what you come up with and happy hacking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bb7e60c6aaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Emotion and Spotify “Mood Music” Project [API Smash]]]></title>
            <link>https://medium.com/@david_13998/microsoft-emotion-and-spotify-mood-music-project-api-smash-6cb9aff8d604?source=rss-94d94b1711d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cb9aff8d604</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[spotify]]></category>
            <dc:creator><![CDATA[David Noah]]></dc:creator>
            <pubDate>Tue, 31 Jan 2017 17:31:14 GMT</pubDate>
            <atom:updated>2017-01-31T18:37:18.107Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/844/0*CU-co_JbPJro6XYm.png" /></figure><p>One of coolest things about APIs is seeing what you can build when you smash them together. We built a script that identifies an emotion from an image (with <a href="https://goo.gl/U2K4eu">Microsoft’s Emotion API</a>), then recommends a musical playlist based on the emotion identified (using <a href="https://goo.gl/vOzVNt">Spotify’s Public API</a>). We’re calling it Mood Music after the team universally vetoed “Spot-motion” (boo!).</p><p>Check it out!</p><p><a href="https://www.youtube.com/watch?v=HZzEoeq3M_w&amp;feature=youtu.be">https://www.youtube.com/watch?v=HZzEoeq3M_w&amp;feature=youtu.be</a></p><p>You can check out the <a href="https://github.com/RapidSoftwareSolutions/APISmash-MicrosoftEmotion-SpotifyPublic/blob/master/script.js">project on GitHub</a>, but here’s the code:</p><pre>const RapidAPI = new require(&#39;rapidapi-connect&#39;);<br>const rapid = new RapidAPI(&#39;EmotionSpotify&#39;, &#39;###RapidAPI project ID###&#39;);<br>let open = require(&#39;open&#39;);<br><br>let imageUrl = process.argv[2];<br><br>rapid.call(&#39;MicrosoftEmotionAPI&#39;, &#39;getEmotionRecognition&#39;, {<br>  // Your Microsfot EmotionAPI substription key (See Docs: <a href="https://rapidapi.com/package/MicrosoftEmotionAPI/docs)">https://rapidapi.com/package/MicrosoftEmotionAPI/docs)</a><br>  &#39;subscriptionKey&#39;: &#39;###Microsoft Emotion Subscription Key####&#39;,<br>  // This is the URL of the facial image to be interpreted<br>  &#39;image&#39;: imageUrl<br><br>}).on(&#39;success&#39;, (payload) =&gt; {<br>  // The MicrosoftEmotionAPI returns a confidence score for happiness, sadness, surprise, anger, fear, contempt, disgust or neutral.<br>  // The emotion detected should be interpreted as the emotion with the highest score, as scores are normalized to sum to one.<br>  // I built a simple loop to find the emotion detected.<br>  let scores = payload[0].scores;<br>  let strongestEmotion = &quot;&quot;;<br>  let emotionScore = 0;<br>  for (var key in scores) {<br>    if (scores[key] &gt; emotionScore) {<br>      emotionScore = scores[key];<br>      strongestEmotion = key;<br>    }<br>  }<br><br>  rapid.call(&#39;SpotifyPublicAPI&#39;, &#39;searchPlaylists&#39;, {<br>  // strongestEmotion should now equal the emotion detected in the photo<br>  &#39;query&#39;: strongestEmotion,<br>  &#39;market&#39;: &#39;&#39;,<br>  // I limit the results to 1 for simplicity. For this test, I&#39;m just returning the top result<br>  &#39;limit&#39;: &#39;1&#39;,<br>  &#39;offset&#39;: &#39;&#39;<br><br>  }).on(&#39;success&#39;, (payload) =&gt; {<br>     // A JSON object is returned containing information about the playlist including the name, URL, and owner.<br>     // Here I have grabbed the playlist&#39;s URL and opened it in the browser using the npm package &quot;open&quot;<br>     open(payload.playlists.items[0].external_urls.spotify);<br>  }).on(&#39;error&#39;, (payload) =&gt; {<br>     console.log(&quot;Spotify Playlist Query Error&quot;);<br>  });<br>}).on(&#39;error&#39;, (payload) =&gt; {<br>  console.log(&quot;Microsoft Emotion Error&quot;);<br>});</pre><p>Here’s how we built it.</p><h3><strong>Connect to Microsoft Emotion API</strong></h3><h4><strong>How the Microsoft Emotion API Works</strong></h4><p>First things first, you’ll want to connect to <a href="https://goo.gl/FwPSxs">Microsoft’s Emotion API</a>. This API scans faces in images and video for the following emotions: anger, contempt, disgust, fear, happiness, neutral, sadness, and surprise. Why these sentiments? Supposedly, these emotions are expressed universally across cultures.</p><p>When you call the API, it will return a confidence score from 0–1 for each emotion. Here’s what happens when the API analyzes the very happy Richard Hendricks (actor Thomas Middleditch) from <em>Silicon Valley.</em></p><figure><img alt="silicon-valley-richard-hendricks-api" src="https://cdn-images-1.medium.com/max/838/0*OjMJudlgURsdzVq-.png" /></figure><p>As you can see in the image above, the API identified “happiness” as the dominant emotion with a score of 0.99. Note — confidence scores will always add up to 1. Even if the emotions are more ambiguous than this smiling picture, the API will assign weighted confidence scores across each emotion.</p><h3><strong>How to Connect to the Microsoft Emotion API</strong></h3><p>Now that you understand how the API works, let’s make some calls! Here’s what you’ll need to do.</p><h4><strong>Step 0: Get the Microsoft Emotion subscriptionKey</strong></h4><p>To make an API call, you’ll first need to sign up for a Microsoft account and get a subscriptionKey by doing the following:</p><ol><li>Go to the <a href="https://www.microsoft.com/cognitive-services/en-us/emotion-api">Microsoft’s Emotion API page</a></li><li>Create a <a href="https://www.microsoft.com/cognitive-services/en-US/subscriptions">Microsoft account</a> or log into an existing account</li><li>In the Request New Trials list, choose “Emotion — Preview” to create new subscription</li><li>In <strong>Key</strong> section choose Key1 or Key2 and press “show” or “copy” to see the subscriptionKey. These keys are interchangeable and either can be used for our purposes</li></ol><p>The process is pretty straightforward, but there are two places where one might get tripped up.</p><ol><li>Microsoft has multiple cognitive services APIs, including the <a href="https://goo.gl/ynYEB3">Computer Vision API </a>(identifies and tags objects in images) and the <a href="https://goo.gl/mRgugR">Face API</a> (isolates faces from images). Each of these APIs needs a <em>separate</em> API key. For this project, be sure to get the API key for Microsoft Emotion API.</li><li>Microsoft may not generate a subscriptionKey until you’ve verified your email. To do this, click the “Send email verification” button if it appears, then click the link in the confirmation email message.</li></ol><figure><img alt="screen-shot-2017-01-24-at-4-47-12-pm" src="https://cdn-images-1.medium.com/max/300/0*_-MVrnnyhDmDGAs7.png" /></figure><p>Once you’ve got the subscriptionKey, you’re ready to call the API.</p><h4><strong>Step 1: Connect to Microsoft Emotion API through RapidAPI</strong></h4><p>While you can call the API manually, we’ve decided to use the RapidAPI tool. RapidAPI lets you test an API call, export the code snippet in your preferred language and call multiple APIs from one abstraction layer.</p><ol><li>Go to <a href="https://goo.gl/FwPSxs">RapidAPI’s Microsoft Emotion API package page</a> and select the <a href="https://goo.gl/hZt9Qe">getEmotionRecognition</a> endpoint</li><li>Enter your Microsoft Emotion subscriptionKey and your image (through an image link or by uploading it directly)</li><li>Click “Test function” to make a call! The API should return an array of confidence scores on emotion detection</li></ol><p>Here’s a quick GIF of how the process works.</p><figure><img alt="microsoft-face-call" src="https://cdn-images-1.medium.com/max/480/0*ryVPY9e__a-OuWKv.gif" /></figure><p>You can export the code snippet used to call the API if you sign in. In this tutorial, we’ll export the snippet with Node.js; however, you can also export the snippet in Ruby, PHP, Python, Objective-C and Java, or cURL.</p><h4><strong>Step 2: Build feedback loop</strong></h4><p>Next, you’ll want to build a feedback loop that grabs an array of scores, iterates through all the emotions and chooses the strongest emotion based on highest score (closest to 1). Even if your picture is emotionally ambiguous, the script will always return at least one emotion.</p><p>We declared three variables: scores, strongestEmotion and emotionScore.</p><ul><li><strong>scores</strong>: Takes payloads and identifies array of emotions from JSON response.</li><li><strong>strongestEmotion</strong>: An empty string variable that will house the emotion with the highest confidence score.</li><li><strong>emotionScore</strong>: Variable used to determine strongestEmotion through the for loop.</li></ul><p>Here’s what the loop looks like with these variables:</p><pre>}).on(&#39;success&#39;, (payload) =&gt; {<br>  // The MicrosoftEmotionAPI returns a confidence score for happiness, sadness, surprise, anger, fear, contempt, disgust or neutral.<br>  // The emotion detected should be interpreted as the emotion with the highest score, as scores are normalized to sum to one.<br>  // I built a simple loop to find the emotion detected.<br>  let scores = payload[0].scores;<br>  let strongestEmotion = &quot;&quot;;<br>  let emotionScore = 0;<br>  for (var key in scores) {<br>    if (scores[key] &gt; emotionScore) {<br>      emotionScore = scores[key];<br>      strongestEmotion = key;<br>    }<br>  }</pre><p>Next, you’ll use the strongestEmotion variable to search Spotify playlists.</p><h3><strong>Connect to the Spotify Public API</strong></h3><p>The <a href="https://goo.gl/vOzVNt">Spotify Public API</a> lets you search Spotify’s giant musical database. The best part? You don’t need a subscription key! Here’s how to get the code snippet from the Spotify API call and incorporate that code into your API smash.</p><h4><strong>Step 0: Test the API call in RapidAPI and export the code snippet</strong></h4><p>This step should feel familiar — it’s the same process we used to call Microsoft’s Emotion API. Head over to the <a href="https://goo.gl/vOzVNt">Spotify Public API</a> package. Next, pick the searchPlaylists endpoint. Make a test call by typing in an emotion in the query parameter (ex. “surprise”) and clicking “Test Function.” The whole process literally takes ten second — we timed it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*huRlIs0cRIDRXBXuRM7UBg.gif" /></figure><p>Bam! You’ve just called the Spotify API. Now, we’ll copy the code snippet and export it into your script.</p><h4><strong>Step 1: Add the Spotify Public API call to your script</strong></h4><p>To put it all together, we’ll fill in the query parameter for the Spotify API call with the strongestEmotion variable. The code snippet will look like this:</p><pre>rapid.call(&#39;SpotifyPublicAPI&#39;, &#39;searchPlaylists&#39;, {<br>  &#39;query&#39;: strongestEmotion,<br>  &#39;market&#39;: &#39;&#39;,<br>  // I limit the results to 1 for simplicity. For this test, I&#39;m just returning the top result<br>  &#39;limit&#39;: &#39;1&#39;,<br>  &#39;offset&#39;: &#39;&#39;</pre><p>The payload returns lots of information about the playlist that we don’t need for this project. Grab the external URL from top result with the snippet: payload.playlists.items[0].external_urls.spotify</p><blockquote>Bonus tip: we added the npm package “open” so the playlist external link opens in your browser automatically. Just run npm install-save open in terminal or visit <a href="https://www.npmjs.com/package/open">this link</a> for more info.</blockquote><h3><strong>Congrats!</strong></h3><p>That should do it! You’ve just built an API Smash.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*NmDTnqZrRL8BgUFb." /></figure><p>You can reference your code with our <a href="https://github.com/RapidSoftwareSolutions/APISmash-MicrosoftEmotion-SpotifyPublic/blob/master/script.js">project on GitHub</a>. f you want to build another API Smash, check out our <a href="https://goo.gl/WyUlWr">Text-A-GIF project</a> using GIPHY and Twilio.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cb9aff8d604" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>