Typhoeus VS httparty

In fact, because the metric is clearly "number of stars", it suggests you two libraries which are either not maintained in almost 3 years, or that haven't had a release in 3 years and a commit in 10 months, despite both of them having a buttload of open issues.

Have you had a play with typhoeus by any chance? It's a wrapper over libcurl, so you get OS threads for free - which is kind of nice.

I would grab a gem like httparty, and dive into the API docs and see what you can do.

HTTParty — Used to make HTTP requests and fetch the required data.

Usually, my ruby HTTP library of choice is HTTParty but I wanted to set this up using the ruby Net::HTTP lib to keep from introducing another dependency.

Everyone here seems to have misread what you wanted. From my interpretation, you are trying to upload a csv somewhere, using an api. With ruby, you can either do it with a built in library or one of the nice http gems. Someone suggested using Python with a builtin library called requests which isn't actually built in, so I'm also going to go with a library that isn't built in. httparty

My go-to is HTTParty for most cases. As a simple example for a one-off request:

I'm too tied to the implementation. If one day I decide to use Faraday or HTTParty as my HTTP clients instead of Net::HTTP, this test will fail.

httparty gem

Now we ensured the right meta data is added to the emails with a custom metatag, let's setup the Postmark API to retrieve the email data an show it in our application. The first step is to add a gem so we can send HTTP requests to the Postmark API. There are several good gems for this, I use the httparty gem. So add this to the Gemfile: