<?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 Heather Kopenski on Medium]]></title>
        <description><![CDATA[Stories by Heather Kopenski on Medium]]></description>
        <link>https://medium.com/@heatherkopenski?source=rss-b0623a80a5f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dd-yhM5iu4RPywEg.</url>
            <title>Stories by Heather Kopenski on Medium</title>
            <link>https://medium.com/@heatherkopenski?source=rss-b0623a80a5f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:23:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@heatherkopenski/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[There’s an API for That]]></title>
            <link>https://medium.com/@heatherkopenski/theres-an-api-for-that-2dd06d9e554?source=rss-b0623a80a5f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dd06d9e554</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Heather Kopenski]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 20:56:01 GMT</pubDate>
            <atom:updated>2018-03-21T20:56:01.771Z</atom:updated>
            <content:encoded><![CDATA[<p>Before I started my road to code, I had a dream of building really cool web apps with functionality far more complex than my then-compressed mind could fathom. Before having even heard the term ‘schema’, I went about filling in excel documents with data that I wanted to use in these afore mentioned “really cool web apps”. I wanted my app to give restaurant recommendations of a certain quality to foodies traveling to new cities. As I was making my list of all my favorite restaurants and their relevant information, I thought to myself: “There has to be a better way to do this. After all, I’m copying and pasting most of this from Yelp…”</p><p>Enter Application Programming Interfaces.</p><p>As I progressed in my journey to becoming a Javascript developer, I came across APIs, and all of the magic and mystery they possess. According to <a href="https://en.wikipedia.org/wiki/Application_programming_interface">Wikipedia</a>, an API is defined as “a set of subroutine definitions, protocols, and tools for building application software.” Cool. I’ll be honest, not so long ago, those words would have meant nothing to me.</p><p>So to those of you who are where I was a few months ago, I’m here for you. What Wikipedia is trying to say, essentially, is that APIs are building blocks, provided by various resources, and used by developers in the production of their own applications. APIs add functionality and data resources to your project that would otherwise be near impossible to come by for many developers. For instance, instead of spending hours filling in my restaurant spreadsheet until I had every decent restaurant in New York City on there, I could just implement <a href="https://www.yelp.com/developers/documentation/v3/get_started">Yelp’s Fusion API</a> and have access to not only every restaurant in New York, but millions of local businesses across 32 countries, all of their customer reviews, ratings, pictures of lattes, and more!</p><p>But it’s not just access to data that APIs offer. Do you want image analysis functionality? There’s an API for that. Want to add a shopping cart to your site? There’s an API for that. There’s even a <a href="http://funtranslations.com/api">Yoda translator API</a>. You read that right.</p><p>So now you can plug a few APIs into your application, code up how you want to interact with the data or functionality they provide, and <em>voilá</em>! Many popular APIs provide super helpful documentation to walk you through implementing them into your application. Most start off the same, requiring you to register your app, like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lhhqaS1AIFbh5BtCH55N8Q.png" /></figure><p>Once you do that, you are provided with a Client ID and Client Secret or API Key. Store these in a secrets file on your application (that you .gitignore, of course) and start making API requests!</p><p>APIs simplify the production process of any application by abstracting the functionality that it provides. This allows us to use APIs written in any language, regardless of what language we coded our app in. They give us just the data or actions we need to access in order to improve our application without compromising our code in any way.</p><p>Thank you APIs, for all that you do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dd06d9e554" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>