Requirements

• E-goi Account with one of the following plans: Base, Pro, or Corporate
• Valid API Key

Overview

The E-goi Email Validator API allows you to verify email addresses through checks like MX record validation and temporary email detection. This is crucial for maintaining high-quality email data in scenarios such as customer sign-ups, marketing lists, transactional emails, and event registrations. By validating emails before adding them to your E-goi account, you can prevent invalid or disposable addresses from entering your database, ensuring that communications—such as newsletters, order confirmations, or event reminders—reach genuine and active recipients. The API can also be used to regularly audit and clean existing email lists, keeping your contact information accurate and reliable.

Endpoint

URL for API Documentation: https://developers.e-goi.com/transactional/v2/#tag/Utilities/operation/emailValidator

Request URL: https://slingshot.egoiapp.com/api/v2/utilities/emailValidator

Method: POST

Example Payload:

{
  "email": "example@example.com",
  "isMx": false,
  "isTemporaryEmail": false,
  "isDeepMx": false,
  "isInboxCheck": false,
  "isFreemail": false,
  "validateDomain": false
}

Parameter Description

API Responses

The API returns a JSON object with various details about the validated email. Below is an example response and a description of the fields.

Example Response:

{
  "emailValid": "true",
  "emailTemporary": "true",
  "mx": "true",
  "deepMx": "true",
  "inboxCheck": "true",
  "freemail": "true",
  "typo": "true",
  "correctSyntax": "true"
}

Use Cases for Implementing Email Validator

Use Case 1: Email Validation During User Registration

Scenario: During user registration on your platform, you want to validate email addresses to ensure that users provide valid and active email addresses before finalizing their account creation.

Configuration:

• Validation Type: Email Validator
• Required Checks: MX validation, temporary email detection, deep MX validation, inbox check, freemail validation, and domain validation

Request URL: https://slingshot.egoiapp.com/api/v2/utilities/emailValidator

Payload Example:

{
  "email": "newuser@example.com",
  "isMx": true,
  "isTemporaryEmail": true,
  "isDeepMx": true,
  "isInboxCheck": true,
  "isFreemail": true,
  "validateDomain": true
}

Example Response:

{
  "emailValid": "true",
  "emailTemporary": "false",
  "mx": "true",
  "deepMx": "true",
  "inboxCheck": "true",
  "freemail": "false",
  "typo": "false",
  "correctSyntax": "true"
}

Explanation: This setup helps ensure that users provide legitimate and operational email addresses during registration. By performing these validations, you can prevent users from registering with invalid or disposable email addresses, thus reducing the risk of fake accounts and improving communication effectiveness with genuine users.

Use Case 2: Email Validation Before Adding to a List

Scenario: You want to validate email addresses before adding them to your E-goi marketing list to ensure they are genuine and active.

Configuration:

• Validation Type: Email Validator
• Required Checks: MX validation, temporary email detection, deep MX validation, inbox check, freemail validation, and domain validation

Request URL: https://slingshot.egoiapp.com/api/v2/utilities/emailValidator

Payload Example:

{
  "email": "example@example.com",
  "isMx": true,
  "isTemporaryEmail": true,
  "isDeepMx": true,
  "isInboxCheck": true,
  "isFreemail": true,
  "validateDomain": true
}

Example Response:

{
  "emailValid": "true",
  "emailTemporary": "false",
  "mx": "true",
  "deepMx": "true",
  "inboxCheck": "true",
  "freemail": "false",
  "typo": "false",
  "correctSyntax": "true"
}

Explanation: This configuration ensures that only valid, non-temporary, and properly configured email addresses are added to your marketing list. By enabling all the validation checks, you can prevent invalid or problematic emails from affecting your email campaigns, thus improving deliverability and engagement rates.

Use Case 3: Email Verification for Transactional Emails

Scenario: Before sending transactional emails like order confirmations or receipts, you want to ensure that the email address is valid and active to avoid delivery failures.

Configuration:

• Validation Type: Email Validator
• Required Checks: MX validation, temporary email detection, deep MX validation, inbox check, freemail validation, and domain validation

Request URL: https://slingshot.egoiapp.com/api/v2/utilities/emailValidator

Payload Example:

{
  "email": "customer@example.com",
  "isMx": true,
  "isTemporaryEmail": true,
  "isDeepMx": true,
  "isInboxCheck": true,
  "isFreemail": true,
  "validateDomain": true
}

Example Response:

{
  "emailValid": "true",
  "emailTemporary": "false",
  "mx": "true",
  "deepMx": "true",
  "inboxCheck": "true",
  "freemail": "false",
  "typo": "false",
  "correctSyntax": "true"
}

Explanation: By validating email addresses before sending transactional emails, you ensure that important communications such as order confirmations or invoices reach the correct recipients. This reduces the risk of undelivered emails, improving customer satisfaction and operational efficiency.

Final Considerations

The E-goi Email Validator API is a robust tool to ensure that email addresses in your database are valid, reducing issues related to invalid or temporary emails. It’s recommended to enable validations based on your specific use case needs.

Note: Be sure to consider including all required parameters in the payload to avoid validation errors.