The results for single verifications are not stored in our system and are not available on​ the dashboard.
Result Codes
Within the response is a result property containing an integer that correlates to a result code listed int the table below. For more information about result codes visit our help docs.
| Result Integer | Description |
|---|---|
| 0 | Valid |
| 1 | Invalid |
| 2 | Disposable |
| 3 | Catchall |
| 4 | Unknown |
Result Details
The
result_detailsproperty has been depreciated.
| Result Detail Integer | Description |
|---|---|
| 0 | No additional details available |
| 1 | Bad Syntax |
Point of Entry Usage
A common scenario for using the single endpoint is to verify emails at the point of entry; helping to keep your user base or newsletter list clean. At the point of entry, we suggest allowing valid, catchall, and unknown emails to proceed while blocking only disposable and invalid emails. It is important to allow unknown results to proceed as they may occur more frequently with the single endpoint than it does with bulk verification.
Additionally, we’ve found that with some smaller email hosts it is not uncommon to take several seconds (sometimes tens of seconds) to respond. It’s, for this reason, we suggest enforcing a client side timeout of approximately 10 seconds in your HTTP request library (ie: Curl, Guzzle, Httparty, etc…) and treat any timeouts as unknowns.