Bulk Email Verify: Retrieve Job Results
/api/v3/email/batch/file/{jobid}
Bulk Email Verify Retrieve Job Results:
This API helps in retrieving the results of the verification job.
Input: Define a path parameter called jobid with the value from /api/v3/email/batch/verify response.
Output: A JSON object containing jobId,status,totalVerifiedEmails,completedOn,results,error.
Example Response:
{
"jobId": "1000080",
"status": "Complete",
"totalEmailCount": "2",
"completedOn": "2024-01-03 11:33:17.474",
"results": [
{
"statusMessage": "",
"account": "abc",
"domain": "oracle.com",
"status": "valid",
"email": "abc@oracle.com"
},
{
"statusMessage": "email_account_invalid",
"account": "xyz",
"domain": "gmail.com",
"status": "invalid",
"email": "xyz@gmail.com"
}
],
"error": {}
}
Response Atrributes
Each email result will consist of these attributes.
| Field | Description |
|---|---|
Email | The email address you've sent for validation. |
Status | The status of validation. For further information, see the Status section. |
StatusMessage | Additional information about the Status. For further information regarding the status messages, see the Status section. |
Account | The account portion of the email address sent for validation. |
Domain | The domain portion of the email address you've sent for validation. |
Status
Your job results will return a Primary Status (Status) and a Secondary Status (StatusMessage) per email.
Primary Status
Here are the potential primary status types:
| Status | Description |
|---|---|
valid | Email address is a valid account. |
invalid | Email address is not valid. For more information, see the Secondary Status table. |
accept_all | Indicates that the domain always considers their emails are valid, even if they are not. This may be due to a firewall or another spam tool that can remove the message or send a bounce message later. |
unknown | The email address appears to be valid, but the domain isn't responding. This could be a temporary issue if the domain is having problems, if a domain isn't working anymore, or if it's a company firewall blocking access issue. |
Secondary Status
By default, the StatusMessage will return as a blank field unless there is additional information to display. Here are potential secondary status types:
| StatusMessage | Description |
|---|---|
email_address_invalid | The email address format is incorrect. |
email_domain_invalid | The email address is associated with a domain that doesn't exist. |
email_account_invalid | The email account doesn't exist at the given domain. |
mailbox_full_invalid | The inbox for this account is full and can't accept incoming mail. |
disposable | The email address is disposable. |
role_address | The email address was created to support a function such as support@, sales@, and so on. This may be a valid email but typically underperforms compared to individual addresses. |
Request
There's no request body for this operation.
Back to TopResponse
- application/json; charset=UTF-8
200 Response
object