getapi-nl Email Validation API
The Email Validation API from getapi-nl — 3 operation(s) for email validation.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/getapi-nl:getapi-nl-email-validation-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: GetApi Email Validation API
version: 0.0.1
description: '## Authentication
All API endpoints require authentication. Include your API key in every request using **one** of the following methods:
**Option 1 — X-Api-Key header (recommended)**
```
X-Api-Key: ga_live_xxxxxxxxxxxxxxxxxxxx
```
**Option 2 — Bearer token**
```
Authorization: Bearer ga_live_xxxxxxxxxxxxxxxxxxxx
```
You can generate and manage API keys in your dashboard.
## AI & Agent Payments (x402)
Some endpoints support direct payments for AI agents via the **x402** protocol (https://www.x402.org).
No API key or account is needed. Send a normal request without key;
the server will respond with **HTTP 402** and a `PAYMENT-REQUIRED` header:
```
PAYMENT-REQUIRED:
```
This base64 string contains, among other things, `network`, `asset`, `amount`, and `payTo`.
Your agent signs an EIP-3009 *transferWithAuthorization* for the specified `amount` of USDC to that `payTo` address,
encodes the signature as base64, and resubmits the request with:
```
PAYMENT-SIGNATURE:
```
The server verifies the signature via a facilitator, provides the data, and settles the payment on-chain.
The success response includes a `PAYMENT-RESPONSE` header containing the transaction information.
A one-time `nonce` prevents replay attacks. Payments are made in USDC on **Base**;
the price is determined by the `credit_cost` of the endpoint.'
contact:
email: info@wdnoord.nl
x-guidance: 'GetAPI.nl is een Nederlandse API-platform voor lookups en validaties (postcode,
adres, kenteken, BTW, e-mail, KVK, IBAN, energiemaatwerk, overheidsdata). Elke
endpoint accepteert een API key via de X-Api-Key header of Authorization:
Bearer <key>.
Sommige endpoints zijn ook direct betaalbaar voor AI-agents via het x402-protocol
(https://www.x402.org) zonder account of API key: stuur een verzoek zonder key,
de server antwoordt met HTTP 402 en een PAYMENT-REQUIRED header (base64 JSON met
network, asset, amount, payTo). Teken daarna een EIP-3009 transferWithAuthorization
voor het gevraagde bedrag in USDC op Base en hertrail met een PAYMENT-SIGNATURE
header. De server verifieert, levert de data en settleert on-chain.
Tips voor agents:
- Lees eerst de PAYMENT-REQUIRED header van een 402-antwoord; die is leidend.
- Geef altijd de exact door de server gevraagde parameters mee.
- Een endpoint met een "x-payment-info" blok vereist betaling voor gebruik.'
servers:
- url: https://api.getapi.nl
description: GetAPI
security:
- ApiKeyAuth: []
- BearerAuth: []
tags:
- name: Email Validation
paths:
/v1/validate/email:
post:
operationId: validation.email
description: Checks the RFC format and verifies that the domain has a valid DNS or MX record.
summary: Validate an email address
tags:
- Email Validation
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
email:
type: string
maxLength: 255
required:
- email
responses:
'200':
description: Email appears valid
content:
application/json:
schema:
type: object
examples:
- valid: true
email: user@example.com
checks:
format: true
domain_exists: true
has_mx_record: true
is_disposable: false
message: Email address appears valid.
properties:
valid:
type: boolean
email:
type: string
checks:
type: object
properties:
format:
type: boolean
domain_exists:
type: boolean
has_mx_record:
type: boolean
is_disposable:
type: boolean
required:
- format
- domain_exists
- has_mx_record
- is_disposable
message:
type: string
required:
- valid
- email
- checks
- message
'422':
description: Unprocessable content
content:
application/json:
schema:
type: object
examples:
- valid: false
email: invalid@
checks:
format: false
domain_exists: false
has_mx_record: false
is_disposable: false
message: Invalid email format.
properties:
valid:
type: boolean
email:
type: string
checks:
type: object
properties:
format:
type: boolean
domain_exists:
type: boolean
has_mx_record:
type: boolean
is_disposable:
type: boolean
required:
- format
- domain_exists
- has_mx_record
- is_disposable
message:
type: string
required:
- valid
- email
- checks
- message
'402':
description: Payment Required
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.010000'
protocols:
- x402: {}
parameters: []
/v1/validate/email/batch:
post:
operationId: validation.email.batch
description: 'Validates up to 25 email addresses in a single request.
Each address is checked for RFC format and DNS/MX record existence.'
summary: Validate a batch of email addresses
tags:
- Email Validation
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
emails:
type: array
items:
type: string
maxLength: 255
minItems: 1
maxItems: 25
required:
- emails
responses:
'200':
description: Batch validation results
content:
application/json:
schema:
type: object
examples:
- total: 2
valid_count: 1
invalid_count: 1
results:
- valid: true
email: user@example.com
checks:
format: true
domain_exists: true
has_mx_record: true
is_disposable: false
message: Email address appears valid.
- valid: false
email: invalid@
checks:
format: false
domain_exists: false
has_mx_record: false
is_disposable: false
message: Invalid email format.
properties:
total:
type: integer
valid_count:
type: integer
invalid_count:
type: integer
results:
type: array
items:
type: object
properties:
valid:
type: boolean
email:
type: string
checks:
type: object
properties:
format:
type: boolean
domain_exists:
type: boolean
has_mx_record:
type: boolean
is_disposable:
type: boolean
required:
- format
- domain_exists
- has_mx_record
- is_disposable
message:
type: string
required:
- valid
- email
- checks
- message
required:
- total
- valid_count
- invalid_count
- results
'422':
$ref: '#/components/responses/ValidationException'
'402':
description: Payment Required
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.010000'
protocols:
- x402: {}
parameters: []
/v1/validate/email/disposable:
post:
operationId: validation.email.disposable
description: 'Checks the domain against a continuously updated blocklist of known
throwaway email services (Mailinator, Guerrilla Mail, 10minutemail, etc.).'
summary: Disposable email domain checker
tags:
- Email Validation
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
email:
type: string
maxLength: 255
required:
- email
responses:
'200':
description: Domain check result
content:
application/json:
schema:
type: object
examples:
- disposable: false
email: user@example.com
domain: example.com
message: This domain is not known as disposable.
- disposable: true
email: user@mailinator.com
domain: mailinator.com
message: This email uses a known disposable/temporary domain.
properties:
disposable:
type: boolean
email:
type: string
domain:
type: string
message:
type: string
required:
- disposable
- email
- domain
- message
'422':
$ref: '#/components/responses/ValidationException'
'402':
description: Payment Required
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.010000'
protocols:
- x402: {}
parameters: []
components:
responses:
ValidationException:
description: Unprocessable content
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code.
message:
type: string
description: Human-readable error message.
errors:
type: object
description: A detailed description of each field that failed validation.
additionalProperties:
type: array
items:
type: string
required:
- error
- message
- errors
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-Api-Key
BearerAuth:
type: http
scheme: bearer