4 Ways to Parse a JSON API with Ruby

October 27, 2015
Written by


The Ruby Toolbox lists no less than 25 HTTP clientsLet’s look at how to retrieve and parse JSON results from a RESTful API using the four most popular Ruby HTTP libraries.

The four code snippets below will:

  1. Define a URL to be parsed. We’ll use the Spotify API because it allows requests without authentication.
  2. Make an HTTP GET request to that URL.
  3. Parse the JSON result. 

Each snippet is a different path to the same destination; if you  pp the result from any of them, you’ll see a hash with Spotify search results: 


Once you have tried a few, head over to our documentation site and try some Ruby Quickstarts. But for now, onward!


net/http is built into the Ruby standard library. There’s no gem to install and no dependencies to cause headaches down the road. If you value stability over speed of development, this is the right choice for you (for example, the twilio-ruby gem is built on net/http).

Unsurprisingly, using Net/http can require more work than using the gems built on top of it. For example, you have to create a URI object before making the HTTP request.

require 'net/http'
require 'json'

url = 'https://api.spotify.com/v1/search?type=artist&q=tycho'
uri = URI(url)
response = Net::HTTP.get(uri)


net/http feels cumbersome and spartan at times. HTTParty was built on top of net/http in order to “Make HTTP fun again.” It adds a lot of convenience methods and can be used for all manners of HTTP requests. 

It also works quite nicely with RESTful APIs. Check out how calling parsed_response on a response parses the JSON without explicitly using the JSON library:

gem install httparty

require 'httparty'

url = 'https://api.spotify.com/v1/search?type=artist&q=tycho'
response = HTTParty.get(url)

HTTParty also offers a command line interface — useful during development when trying to understand the structure of HTTP responses.


rest-client is “a simple HTTP and REST client for Ruby, inspired by the Sinatra’s microframework style of specifying actions: get, put, post, delete.” Like HTTParty, it’s also built upon net/http. Unlike HTTParty, you’ll still need the JSON  library to parse the response.

gem install rest-client

require 'rest-client'
require 'json'

url = 'https://api.spotify.com/v1/search?type=artist&q=tycho'
response = RestClient.get(url)


Faraday is for developers who crave control. It has middleware to control all aspects of the request/response cycle. While rest-client and HTTParty lock you into net/http, Faraday lets you choose from seven HTTP Clients. For instance, you can use EventMachine for asynchronous request. (For the others, check out the github repo).

That customization means that our Faraday code snippet is more involved. Before we make our HTTP request and parse our results, we have to:

  1. Choose an HTTP adapter. The default is net/http.
  2. Identify the response type. In this case we’ll use JSON, but you could also use XML or CSV.  

gem install faraday
gem install faraday_middleware

require 'faraday'
require 'faraday_middleware'

url = 'https://api.spotify.com/v1'

conn = Faraday.new(url: url) do |faraday|
  faraday.adapter Faraday.default_adapter
  faraday.response :json

response = conn.get('search', type: 'artist', q: 'tycho')

You’ll notice that we pass our query as optional parameters on the  get  method instead of concatanating them into the URL string. And because we’ve already told Faraday that the response is going to be JSON, we can call response.body and get back a parsed hash.

Wrapping Up

The Ruby ecosystem offers a ton of options for interacting with JSON APIs. While these approaches are similar for the simplest of GET requests, the differences become more apparent as your HTTP requests grow in complexity. Play around and see which one best fits your needs.

Did we miss your favorite library? Let us know in the comments.

Try our Ruby Quickstarts, or our other Twilio Guides and Tutorials.

Many thanks to Phil Nash and Matt Makai for their contributions to this post. And thanks to updog and rjungemann for their feedback on /r/ruby