Validate emails

curl --request POST \
  --url https://api.generect.com/api/v1/email/validate/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "emails": [
    "john@acme.com",
    "jane@corp.io"
  ]
}
'

{
  "data": {
    "results": [
      {
        "email": "john@acme.com",
        "status": "VALID",
        "is_deliverable": true,
        "is_catch_all": false,
        "is_disposable": false,
        "risk_score": 0.1
      }
    ]
  },
  "meta": {
    "amount_charged": 0.005
  }
}

POST

validate

Validate emails

curl --request POST \
  --url https://api.generect.com/api/v1/email/validate/ \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "emails": [
    "john@acme.com",
    "jane@corp.io"
  ]
}
'

{
  "data": {
    "results": [
      {
        "email": "john@acme.com",
        "status": "VALID",
        "is_deliverable": true,
        "is_catch_all": false,
        "is_disposable": false,
        "risk_score": 0.1
      }
    ]
  },
  "meta": {
    "amount_charged": 0.005
  }
}

Use Case:

Clean and verify email lists to improve campaign success rates and lower bounce rates.

Pricing

This is a billable endpoint — you are charged for each email validated.

Your price decreases automatically as your lifetime spend grows. Check your current tier and pricing →

Authorizations

Authorization

string

header

required

Use the required Token prefix. Example: Authorization: Token xxxxxxxxx

Body

application/json

emails

string[]

required

Response

Validation results

data

object[]

One validation result per submitted email — see the example.

​Use Case:

​Pricing

Authorizations

Body

Response

Use Case:

Pricing