How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Enrich Email Validation API

The Email Validation API from Enrich — 4 operation(s) for email validation.

Enrich Email Validation API is one of 18 APIs that Enrich publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Email Validation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://dev.enrich.so/api/v3.

4 operations 4 paths 26 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://dev.enrich.so/api/v3
Authentication
API Key, HTTP Bearer, apikey, bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 4

Enrich Email Validation API declares 4 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyHeader). It accepts HTTP bearer tokens (BearerToken). It defines a apikey scheme (apiKey). It defines a bearer scheme (bearerAuth).

  • ApiKeyHeader — API key in the x-api-key header. Documented at https://doc.enrich.so/authentication-1951026m0
  • BearerToken — The same API key sent as an Authorization: Bearer token.
  • apiKey — Your API key. Keys start with sklive and are 64 characters long.
  • bearerAuth — Alternative — send the same key as a Bearer token: Authorization: Bearer sklive...

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Email Validation 4
POST
/email-validation
Validate a single email
validateEmail body → 200400401402429500
POST
/email-validation/batch
Validate emails in batch
batchValidateEmails body → 200400401402429500
GET
/email-validation/batch/{batchId}
Check batch validation progress
getEmailValidationBatchStatus 1 param → 200401404429
GET
/email-validation/batch/{batchId}/results
Get batch validation results
getEmailValidationBatchResults 3 params → 200401404429

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are EmailValidationResult_2 (9 properties), EmailValidationResult (9 properties), BatchResultsMeta_2 (6 properties), BatchResultsMeta (6 properties). Each schema is shown below with its type and property counts.

EnrichmentMeta
object
Metadata included with every enrichment response
4 properties
EmailValidationResult
object
The result of validating a single email address
9 properties 5 required
BatchStatusResponse
object
3 properties 2 required
EmailValidationRequest
object
1 property 1 required
BatchStatusData
object
Progress information for a batch job
5 properties 2 required
ErrorEnvelope
object
RFC 9457 Problem Details error response.
5 properties 3 required
BatchSubmitData
object
Returned when you submit any batch job
5 properties 3 required
EmailValidationResponse
object
3 properties 2 required
EmailValidationBatchResultsResponse
object
3 properties 2 required
BatchResultsMeta
object
Metadata returned when you fetch batch results (includes credit settlement)
6 properties
BatchSubmitResponse
object
3 properties 2 required
BatchSubmitMeta
object
Metadata returned when you submit a batch job
4 properties
BatchEmailValidationRequest
object
2 properties 1 required
EnrichmentMeta_2
object
Metadata included with every enrichment response
4 properties
EmailValidationResult_2
object
The result of validating a single email address
9 properties 5 required
BatchStatusResponse_2
object
3 properties 2 required
EmailValidationRequest_2
object
1 property 1 required
BatchStatusData_2
object
Progress information for a batch job
5 properties 2 required
ErrorEnvelope_2
object
RFC 9457 Problem Details error response.
5 properties 3 required
BatchSubmitData_2
object
Returned when you submit any batch job
5 properties 3 required
EmailValidationResponse_2
object
3 properties 2 required
EmailValidationBatchResultsResponse_2
object
3 properties 2 required
BatchResultsMeta_2
object
Metadata returned when you fetch batch results (includes credit settlement)
6 properties
BatchSubmitResponse_2
object
3 properties 2 required
BatchSubmitMeta_2
object
Metadata returned when you submit a batch job
4 properties
BatchEmailValidationRequest_2
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enrich-so-email-validation-api-openapi.yml Raw ↑

Other APIs Enrich publishes across the network.

Enrich Email Finder API
Enrich Lead Finder API
Enrich Phone Finder API
Enrich Teams API
Enrich People Search API
Enrich Authentication API
Enrich Company Followers API
Enrich Company Followers/Count Estimation API
Enrich Enrich API
Enrich IP to Company API
Enrich Reverse Email Lookup API
Enrich Wallets API
Where this information came from

This is an independent, third-party profile of Enrich Email Validation API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.