make your own api

Posted on
<script src="2018-07-12-make-your-own-api_files/libs/htmlwidgets-1.6.2/htmlwidgets.js"></script> <script src="2018-07-12-make-your-own-api_files/libs/d3-3.3.8/d3.min.js"></script> <script src="2018-07-12-make-your-own-api_files/libs/dagre-0.4.0/dagre-d3.min.js"></script> <script src="2018-07-12-make-your-own-api_files/libs/mermaid-0.3.0/dist/mermaid.slim.min.js"></script> <script src="2018-07-12-make-your-own-api_files/libs/chromatography-0.1/chromatography.js"></script> <script src="2018-07-12-make-your-own-api_files/libs/DiagrammeR-binding-1.0.10/DiagrammeR.js"></script>

What’s in an API?

An API is an application programming interface. It is basically a set of instructions for interfacing with a server. When working with web data you don’t need to render an entire website for viewing- you just want to get some raw data. You can do this through the API (often a REST) and talk to the server directly. Within this API you send a set of instructions that says what data you want and in what form you want it in. Then it sends you the data.

library(DiagrammeR)

mermaid("
graph LR
  Server-->Browser
Browser -->Server
  Browser-->Viewer
  Server-->API
  API-->Server
", height = 200)
<script type="application/json" data-for="htmlwidget-a07dc4b0b53de6677091">{"x":{"diagram":"\ngraph LR\n Server-->Browser\nBrowser -->Server\n Browser-->Viewer\n Server-->API\n API-->Server\n"},"evals":[],"jsHooks":[]}</script>

What about internally?

Often times in the business world, we don’t necessarily access internal data though a REST API (unless you are Amazon) 1.

If your company does internal APIs that is wonder. Quite honestly they aren’t too hard to set up and with a little help from plumber a data scientist could use R to set an API up. Not the best idea but it still stands, it can be done.

But what about common drives

This is where I have developed some APIs for myself and others. Perhaps data is stored in flatfiles on a common drive. Instead of everyone mapping to the drive at the start of each script, write a package to function like your own API, something like:

get_internal_data <- function(data_set){
  path <-"path/to/internal/directory"

  available_files <- list.files(path, pattern = ".csv$") %>%
    gsub(pattern = ".csv", replacement = "", .)

  if(!data_setv %in% available_files){
    stop("Data set not available")
  }

  df <- read_csv(file.path(path, data_set))

  df
}

Now anyone can use your function to call a data set. This saves some typing, and if you use the absolute mappings then this makes it easier to share internal code. Additionally, you could wrap this function, perhaps with several other to different data sources into a package. That package can then be shared and everyone will have easy access to the data. If the storage of items changes, then you can update the package details (via a version control system) and have everyone load the new package. This automatically changes the internals so their function to access the data is redirected to the new location!

This same kind of method could be used for accessing internal databases. Set you the connection and it provides you the tools to work with internal tools in an API-like fashion.

  1. The story behind this is that Jeff Bezos in his brilliance made Amazon access everyones data internally through APIs. This vision allowed them to speed past the competition with Amazon web services because they had basically been doing it for years. By building this kind of infrastructure early, learning through bumps and bruising along the way they were ready to present an internal architecture to the public and make loads of money on it. More here ↩


Citation

BibTex citation:

@online{dewitt2018
author = {Michael E. DeWitt},
title = {make your own api},
date = 2018-07-12,
url = {https://michaeldewittjr.com/articles/2018-07-12-make-your-own-api},
langid = {en}
}

For attribution, please cite this work as:

Michael E. DeWitt. 2018. "make your own api." July 12, 2018. https://michaeldewittjr.com/articles/2018-07-12-make-your-own-api