Email Check

Endpoint Overview

POST /api/v1/employment/email-check

Description

The Email Check API validates and verifies email addresses to determine their authenticity, deliverability, and security status. This endpoint performs comprehensive analysis of an email address, checking its syntax, domain validity, SMTP connectivity, and potential security risks. It helps organizations reduce fraud, improve communication reliability, and maintain data quality by ensuring email addresses are valid and safe to use.

Key Benefits

Reduces bounce rates by validating email deliverability before sending communications

Prevents fraud by identifying temporary, catch-all, or suspicious email addresses

Improves data quality by verifying email syntax and domain validity

Enhances security by detecting potentially risky or compromised email accounts

Use Cases

Financial Services

E-commerce

HR & Recruitment

Verify customer email addresses during account registration to reduce fraud

Validate email addresses before sending sensitive financial documents

Ensure reliable communication channels for transaction notifications

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token authentication using JWT format
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
email	String	Yes	The email address to validate and verify

Example Request

{
    "email": "vishalrathore9965@gmail.com"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the email check results
data.client_id	String	Unique identifier for this email check request
data.email	String	The email address that was checked
data.status	String	Overall safety status of the email ("safe" or other status indicators)
data.valid	Boolean	Whether the email is valid overall
data.valid_syntax	Boolean	Whether the email follows correct syntax rules
data.accepts_mail	Boolean	Whether the email address can receive mail
data.results	Boolean	Overall check result
data.smtp_connected	Boolean	Whether SMTP connection was successful
data.domain	String	The domain portion of the email address
data.domain_age	String	Age of the domain (null if unavailable)
data.domain_registrar	String	Domain registrar information (null if unavailable)
data.username	String	The username portion of the email address
data.disabled	Boolean	Whether the email account is disabled
data.organization	String	Organization associated with the email (null if unavailable)
data.organization_match	String	Organization match status (null if unavailable)
data.person_match	String	Person match status (null if unavailable)
data.is_temporary	Boolean	Whether the email is from a temporary email service
data.is_catch_all	Boolean	Whether the domain accepts all emails regardless of username
data.mx_records	Array	List of mail exchange records for the domain
status_code	Integer	HTTP status code of the response
success	Boolean	Whether the API request was successful
message	String	Human-readable status message
message_code	String	Machine-readable status code

Example Successful Response

{
    "data": {
        "client_id": "email_check_PUTbQENdjpuytwsZLmnh",
        "email": "vishalrathore9965@gmail.com",
        "status": "safe",
        "valid": true,
        "valid_syntax": true,
        "accepts_mail": true,
        "results": true,
        "smtp_connected": true,
        "domain": "gmail.com",
        "domain_age": null,
        "domain_registrar": null,
        "username": "vishalrathore9965",
        "disabled": false,
        "organization": null,
        "organization_mactch": null,
        "person_match": null,
        "is_temporary": false,
        "is_catch_all": false,
        "mx_records": [
            "alt2.gmail-smtp-in.l.google.com.",
            "alt1.gmail-smtp-in.l.google.com.",
            "gmail-smtp-in.l.google.com.",
            "alt4.gmail-smtp-in.l.google.com.",
            "alt3.gmail-smtp-in.l.google.com."
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Email Format

Authentication Error

{
    "data": null,
    "status_code": 400,
    "success": false,
    "message": "Invalid email format",
    "message_code": "invalid_email_format"
}

The provided email address does not follow valid email syntax.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to avoid exposing sensitive information

Validate and sanitize email inputs before sending to the API

Use HTTPS for all API communications to ensure data encryption

User Experience Guidelines

Implement real-time email validation during user registration to provide immediate feedback

Display user-friendly error messages when invalid emails are detected

Consider implementing progressive validation that checks syntax first before performing full verification

Add a loading indicator during email verification as the check may take a few seconds

Code Samples

cURL

Python

Node.js

Related APIs

Phone Number Verification API: Validates and verifies phone numbers for authenticity and deliverability

Address Verification API: Validates physical addresses for accuracy and deliverability

Identity Verification API: Verifies user identity through multiple data points

Compliance and Legal Considerations

When using this API, ensure compliance with data protection regulations such as GDPR, CCPA, or other applicable laws in your jurisdiction. Email verification should be conducted with user consent and for legitimate business purposes. Store verification results securely and maintain appropriate data retention policies.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/employment/email-check' \ --header 'Authorization: Bearer TOKEN' \ --header 'Content-Type: application/json' \ --data-raw '{ "email": "vishalrathore9965@gmail.com" }'

{ "data": { "client_id": "email_check_PUTbQENdjpuytwsZLmnh", "email": "vishalrathore9965@gmail.com", "status": "safe", "valid": true, "valid_syntax": true, "accepts_mail": true, "results": true, "smtp_connected": true, "domain": "gmail.com", "domain_age": null, "domain_registrar": null, "username": "vishalrathore9965", "disabled": false, "organization": null, "organization_mactch": null, "person_match": null, "is_temporary": false, "is_catch_all": false, "mx_records": [ "alt2.gmail-smtp-in.l.google.com.", "alt1.gmail-smtp-in.l.google.com.", "gmail-smtp-in.l.google.com.", "alt4.gmail-smtp-in.l.google.com.", "alt3.gmail-smtp-in.l.google.com." ] }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Email Check

Email Check#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

Email Check

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples