Verify your 1st Email

💡

In this document, I’ll guide you through how to start verifying emails with Reacher. This document is meant for beginners. If you know how to send API requests, this guide probably isn’t for you.

Step 1: Download Postman

Reacher’s main product is an API, which means there’s no pretty user interface to interact with it. But it also means that it integrates very easily with your or your team’s other tools.

In this guide, we’ll download Postman, which is a user interface to interact with any APIs, including Reacher’s.

Head to https://www.postman.com/ and download their desktop application for your operating system. After installation, open the app and you should see something like:

Step 2: Create a new Collection

Postman holds individual API calls under Collections. We can create on called “Reacher Demo” by following the 3 steps below.

You can retrieve your secret API key from your Reacher Dashboard, it is called the AUTH_TOKEN, and is a single line alphanumerical code with some dashes in the middle.

Congratulations! You have created a Collection called “Reacher Demo” in Postman. The next step is to add an API request to that collection: that API request will do the actual email verification.

Step 3: Create an API request to verify an email

Each email verification on Reacher is done via what’s called an “API request”, which basically means a network request to Reacher’s servers to verify if an email exists or not. Let’s set up this API request.

If you want to copy-paste it instead of typing it, the URL to enter is:

https://api.reacher.email/v0/check_email

You’ll also find it in your Reacher Dashboard.

In the “Body”, we’ll put the email we want to verify.

If you want to copy-paste that multiline text, it’s just below:

{
	"to_email": "amaury@reacher.email"
}

Everything is set! You’re ready to make the API request to verify the email now.

Step 4. Check out the result

Now that the API request is ready, all you need to do is execute it.

The is_reachable field can take 4 values:

safe: the email exists and it’s safe to send emails to it.

risky: the email exists, but there’s a risk of hard-bounce when sending an email to it.

invalid: the email does not exist.

unknown: Reacher cannot figure out if the email exists or not.

To read more about these 4 values, or to understand the other fields, please check out 📬Email Attributes inside JSON.

And you’re done 🚀! Feel free to change the to_email value in the Body, to verify other emails.

I encountered a problem 😢

If you had trouble following this guide, or if you got an error message, simply send an email to ✉️ amaury@reacher.email, ideally with a screenshot of your error message.