The FDIC recently exposed a JSON-over-HTTP API behind its BankFind website. This gem makes that API easy to use from Ruby.

Simple HTTP-based Job scheduling for the cloud.

Ruby client to the INFURA (infura.io) API. Allows HTTP access to ethereum and IPFS nodes.

Simple Ruby wrapper for the Trulia API built on HTTParty

HTTP helper library

Rat Hole is a handy library for creating a rack compliant http proxy that allows you to modify the request from the user and the response from the server.

Simple HTTP server launcher for Rack application (Sinatra, Rails, etc...)

Ruby API wrapper for education.com schoolfinder built with httparty

This gem provides a (hopefully) high quality http parser library that can build request information iteratively as data comes over the line without requiring the caller to maintain the entire body of the request as a single string in memory.

Make HTTP requests and handle its responses using simple method calls. Restool turns your HTTP API and its responses into Ruby interfaces.

This gem offers a shim to connect Rails apps with a Bonsai Elasticsearch cluster. The official Elasticsearch gem package requires some minor configuration tweaks in order to work correctly with Bonsai (namely the client needs to be instantiated with the cluster location and HTTP authentication details), and the process can be somewhat complicated for users who are unfamiliar with the system. The bonsai-elasticsearch-rails gem automatically sets up the Elasticsearch client correctly so users don't need to worry about configuring it in their code or writing an initializer. In order for the gem to work correctly, the application needs an environment variable called `BONSAI_URL`, which is populated with the complete Bonsai Elaticsearch cluster URL, including the HTTP authentication. The cluster URL will follow this pattern: https://user1234:pass5678@cluster-slug-123.aws-region-X.bonsai.io/ On Heroku, this variable is created and populated automatically when Bonsai is added to the application. Heroku users therefore do not need to perform any additional configuration to connect to their cluster after adding the bonsai-elasticsearch-rails gem. Users who are self-hosting their Rails app will need to make sure this environment variable is present: export BONSAI_URL="https://user1234:pass5678@aws-region-X.bonsai.io/" The cluster URL is available via the Bonsai dashboard.

A gem for handling exceptions thrown inside your Rails app. If you include the gem in your application controller, wrangler will render the error pages you configure for each exception or HTTP error code. It will also handle notifying you via email when certain exceptions are raised. Allows for configuration of which exceptions map to which error pages, which exceptions result in emails being sent. Also allows for asynchronous email sending via delayed job so that error pages don't take forever to load (but delayed_job is not required for sending email; wrangler will automatically send email synchronously if delayed_job is not available. . See README for lots of info on how to get started and what configuration options are available.

ApnsGatling is a token based authenitcation APNs HTTP/2 gem.

A simple gem that allows you to sign HTTP requests between two parties with a shared secret key.

Pedal-to-the-metal HTTP client for GET requests

A rack middleware library that allows for cookies to be passed through form parameters. Specifically, it merges the specified form parameters into the Cookie header of an http request. It gets around the problem of having a flash application which interacts with a web application that uses cookie based sessions.

A Ruby wrapper for the Zferral API, based on HTTParty.

Micky makes simple HTTP requests (GET/HEAD), follows redirects, handles exceptions (invalid hosts/URIs, server errors, timeouts, redirect loops), automatically parses responses (JSON, etc.), is very lightweight, and has no dependency.

Enables the creation of scenarios that involve creating a rails project, starting and stoppping of servers, generating projects, editing files, issuing http requests, running of commands, etc. Output is captured as a single HTML file that can be viewed locally or uploaded. Additionally, there is support for verification, in the form of defining assertions based on selections (typically CSS) against the generated HTML.

RiakRest provides structured, RESTful interaction with the HTTP/JSON interface of a Riak[http://riak.basho.com] document data store. RiakRest provides two levels of interaction: Core Client and Resource. Core Client works at the Jiak level and exposes Jiak internals. JiakResource is an abstraction built on top of the Core Client that gives a true RESTful feel.