Blaze Verify Ruby Library

Build Status Maintainability

This is the official ruby wrapper for the Blaze Verify API.


See the Ruby API docs.


Add this line to your application's Gemfile:

gem 'blazeverify'

And then execute:

$ bundle

Or install it yourself as:

$ gem install blazeverify


The library needs to be configured with your account's API key which is available in your Blaze Verify Dashboard. Set BlazeVerify.api_key to its value:


require 'blazeverify'

# set api key
BlazeVerify.api_key = 'live_...'


# verify an email address

Slow Email Server Handling

Some email servers are slow to respond. As a result the timeout may be reached before we are able to complete the verification process. If this happens, the verification will continue in the background on our servers. We recommend sleeping for at least one second and trying your request again. Re-requesting the same verification with the same options will not impact your credit allocation within a 5 minute window.

    "message" => "Your request is taking longer than normal. Please send your request again."

Batch Verification

Start a batch

emails = ['', '', ...]
batch =

# you can optionally pass in a callback url that we'll POST to when the
# batch is complete.
batch =, callback: '')

# start verifying the batch

Get the status / results of a batch

Calling status on a batch will return the status. It will contain the results as well once complete. You can also results to get just the results.

id = '5cfcbfdeede34200693c4319'
batch =

# get status of batch

# gets the results

# get the counts

# returns true / false


After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to


Bug reports and pull requests are welcome on GitHub at