API Reference
Complete reference documentation for the nofakemails email validation API.
Base URL
All API requests should be made to:
https://api.nofakemails.comHTTPS Required
All API requests must be made over HTTPS. Requests made over plain HTTP will be rejected.
API Versioning
The nofakemails API uses URL path versioning. The version is included in the URL path as a prefix (e.g., /v1/).
| Version | Status | Base Path |
|---|---|---|
| v1Latest | Active | /v1/ |
Version Headers
Every API response includes headers indicating supported and deprecated versions:
| Header | Description |
|---|---|
X-API-Versions | List of all supported API versions |
X-Deprecated-Versions | List of deprecated versions (if any) |
Content Type
The API accepts and returns JSON. Always include the appropriate content type header for POST requests:
Content-Type: application/jsonRequest Methods
The API uses standard HTTP methods:
| Method | Description |
|---|---|
| GET | Single email validation |
| POST | Batch email validation |
Quick Links
- Validate Email Endpoint — Single email validation
- Batch Validate Emails — Validate up to 64 emails in one request
- Response Format — Understanding API responses
- Error Codes — Complete error reference
- Rate Limits — Usage limits by tier
- Code Examples — Copy-paste examples in 8 languages