Documentation

Kawaa API documentation

Everything you need to integrate email verification into your application. Our REST API provides real-time and batch verification with layered DNS, MX, and risk checks.

Base URLhttps://api.kawaa.com

Get started

Machine-readable description

The core verification API is described by an OpenAPI 3.1 document at kawaa.com/openapi.json. Generate a client from it, load it into Postman or Insomnia, or hand it to an agent. It covers the endpoints a customer integration uses: verification, jobs, results, activity, deliverability, webhooks, keys and the billing catalogue. It does not yet describe the white-label API, the domain activity lookup or tracking links; their pages here are the reference.

Checked against the running code on every build

Every operation is a route the API actually serves.
Every operation lists the scopes it enforces.
Every error code is one the handlers emit.
Response shapes for credentials, billing fields and job results, where a mistake would cost most. Other fields are described, but not checked exhaustively.

It is not the whole surface: profile and security settings (password, two-factor, sessions), billing and subscription changes and team management are not modelled in it, and have no page here yet either. Connecting HubSpot, Salesforce or Mailchimp from the dashboard is not available yet; those tools work through the API or a CSV upload. The other way round, the email finder, the domain lookup and the billing catalogue are modelled in the document but have no guide on these pages.

API capabilities

Single email verification with real-time results
Batch verification for up to 10,000 emails (plan-dependent)
File upload processing (CSV, TXT)
Webhook notifications for async jobs
Activity data and engagement metrics
Deliverability checks: SPF, DKIM, DMARC, MX, reverse DNS and blocklists

Authentication

Every API request needs a credential: an API key in the X-Api-Key header (or as a bearer token), or the access token an agent receives by signing in with OAuth. See Authentication.

Example request

curl -X POST https://api.kawaa.com/v1/verify \
  -H "X-Api-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"email": "test@example.com"}'

Get your API key from the Dashboard.

Response format

All responses are returned in JSON format with consistent structure. This is the real answer for test@example.com when its DNS lookup succeeds (trimmed): the domain is reserved for documentation and accepts no mail.

Example response

{
  "success": true,
  "data": {
    "email": "test@example.com",
    "status": "invalid",
    "sub_status": "no_mx",
    "quality_score": 10,
    "verification": {
      "syntax_valid": true,
      "domain_exists": true,
      "mx_found": false,
      "greylisted": false
    },
    "flags": {
      "disposable": false,
      "role_account": false,
      "free_provider": false,
      "spam_trap": false,
      "abuse_email": false,
      "honeypot": false,
      "complainer": false,
      "bot_generated": false
    }
  }
}

Ready to get started?

Follow our quick start guide to make your first API call in under 5 minutes.

Quick start guide Try the API playground