VeryFire API Documentation

Welcome to VeryFire API

VeryFire is a powerful email verification API that helps you validate email addresses with minimal effort. Check if an email address or domain is disposable, temporary, has an existing deliverable mailbox, and much more.

🚀 Fast & Reliable

Real-time email validation with comprehensive checks

🔒 Secure

Token-based authentication with credit management

📊 Detailed Results

Get comprehensive data about email validity and deliverability

Getting Started

🔑 Create Your API Credentials
To get started with the VeryFire API, you need to create your API credentials at app.veryfire.io under Account Settings.

Quick Start Guide

Sign up at app.veryfire.io
Navigate to Account Settings
Generate your API token
Start making API requests!

Base URL

https://api.veryfire.io/api

Authentication

All protected API requests require a Bearer token for authentication:

Authorization: Bearer YOUR_API_TOKEN

Required Headers

Accept: application/vnd.api+json
Content-Type: application/vnd.api+json

API Endpoints

GET /credits

Retrieve the current credit balance for the authenticated user.

Headers

Authorization: Bearer YOUR_API_TOKEN
Accept: application/vnd.api+json

Example Request

curl -X GET https://api.veryfire.io/api/credits \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/vnd.api+json"

Example Response

{
  "status": "success",
  "message": "Credits retrieved successfully",
  "data": {
    "credits": 150,
    "user_id": "123"
  }
}

GET /emails/{email}

Validate an email address and get detailed information about its validity, deliverability, and potential issues.

💰 Credit Cost: This endpoint costs 1 credit per request (unless using a supertoken).

URL Parameters

Parameter	Type	Description
`email`	string	The email address to validate

Example Request

curl -X GET https://api.veryfire.io/api/emails/test@example.com \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/vnd.api+json"

Response Fields

Field	Type	Description
valid	boolean	Whether the email has valid syntax (RFC 822)
deliverable	boolean	Whether the email can receive messages
should_block	boolean	Recommendation to block this email (disposable, invalid, etc.)
domain	object	Domain information including MX records, validity, and flags
role	object	Role-based email information (e.g., admin@, support@)

Example Response

{
  "data": {
    "type": "emails",
    "id": "a1b2c3d4e5f6",
    "attributes": {
      "email_hash": "5d41402abc4b2a76b9719d911017c592",
      "valid": true,
      "deliverable": true,
      "should_block": false,
      "domain": {
        "id": 42,
        "name": "example.com",
        "valid": true,
        "disposable": false,
        "automated": false,
        "free": false,
        "mx_found": true,
        "smtp_valid": true,
        "mx_records": [
          {
            "host": "mail.example.com",
            "priority": 10
          }
        ]
      },
      "role": null
    }
  }
}

Understanding Email Validation

Validation Checks

VeryFire performs multiple checks to validate email addresses:

Syntax Validation

Checks if the email follows RFC 822 standards

Domain Verification

Validates the domain exists and is properly configured

MX Record Check

Verifies mail exchange records are present

SMTP Validation

Tests if the mail server is responding

Disposable Detection

Identifies temporary/disposable email services

Role Detection

Identifies role-based addresses (admin@, support@, etc.)

When to Block an Email

The should_block field is set to true when:

The domain is invalid
No MX records are found
SMTP validation fails
The domain is identified as disposable
The domain is automated (catch-all)
The email is a role-based address
The domain is a typo of a common domain

Error Handling

HTTP Status Codes

Status Code	Description
`200`	Success - Request completed successfully
`400`	Bad Request - Invalid parameters
`401`	Unauthorized - Invalid or missing authentication token
`402`	Payment Required - Insufficient credits
`404`	Not Found - Resource doesn't exist
`500`	Internal Server Error - Something went wrong on our end

Error Response Format

{
  "status": "error",
  "message": "Failed to deduct credits",
  "data": "Credit deduction failed"
}

Rate Limits & Best Practices

Credit System

VeryFire uses a credit-based system. Each email verification costs 1 credit. Monitor your credit balance using the /credits endpoint.

Best Practices

Cache Results: Email validation results are cached for 7 days. Repeated checks within this period won't cost additional credits.
Batch Validation: For bulk email validation, contact our support team for optimized solutions.
Handle Errors Gracefully: Always check for insufficient credit errors (402) before processing.
Respect the API: Implement reasonable rate limiting in your application.

Support & Resources

Need help or have questions? We're here to assist you!

📧 Email Support

Contact us for technical support and inquiries

📝 Account Management

Manage your API keys at app.veryfire.io

🔄 API Status

All systems operational