← API network IDENTITY / EMAIL / VERIFICATION / QUALITY

Direct Platform Unversioned / General Availability api.dakidarts.comDirect gateway

Checky Email Verification API

Email validation with syntax, blacklist, DNS and SMTP checks, plus text extraction that validates each discovered address.

Preview examples View on RapidAPI OpenAPI 3.1 ↗ GitHub repository ↗ Release feed ↗

Direct PlatformCH

api.dakidarts.comUnversionedGeneral Availability25ms p955 documented endpoints

DIRECT NATIVE API

Call Checky Email Verification API through the Dakidarts gateway.

0 of 5 endpoints have an upstream URL configured. Other routes return 503 before billing; only send live requests to configured routes. The gateway injects upstream credentials for you.

Live checkout opens after an API route has an upstream URL. Preview examples are available below.

Base URLhttps://api.dakidarts.com/checky-email

AuthenticationX-API-Key: dk_live_...

Default reference pathGET /validate

Commercial modelPay-as-you-go / $0.0050 per call

01 / ACCESS

One key, one gateway

Use a Dakidarts API key with read or write scopes and control which APIs that key can reach.

02 / BILLING

Metered by the call

Wallet credits, plan quotas and organization invoices are settled per request with transparent response headers.

03 / RELIABILITY

Observable by default

Latency, upstream status and execution mode are logged so integration issues are visible before they spread.

RAPIDAPI SPOTLIGHTRapidAPI Marketplace

Also available through RapidAPI.

Keep the direct Dakidarts gateway as your primary route, or use the RapidAPI listing when marketplace billing and key management fit your stack better.

View on RapidAPI Plans, keys and usage stay inside RapidAPI.

CAPABILITIES

Built to disappear into the product.

The best API is the one your team can integrate, observe and then stop thinking about.

Improve contact quality in signup and lead-capture flows

Designed as a composable building block for product teams, internal tooling and automation.

Validate individual addresses with GET or POST

Designed as a composable building block for product teams, internal tooling and automation.

Extract multiple candidate addresses from submitted text

Designed as a composable building block for product teams, internal tooling and automation.

PLATFORM FACTS

The shape of the surface.

Selected facts about coverage, delivery and production readiness.

01Format and blacklist checks

02DNS and SMTP deliverability checks

03Text extraction with per-address validation

FAQ

Answers before you integrate.

Access, billing and integration details for Checky Email Verification API.

What does email verification return? +

Quality and deliverability signals for a supplied email address.

Can it reduce bad sign-ups? +

Yes. It helps screen invalid or risky addresses before they enter your product.

Does it send an email to the address? +

No. The API validates without sending a message from your product.

How do I get access? +

Subscribe on the Dakidarts dashboard, then use an API key with this API in scope.

Is it suitable for CRM hygiene? +

Yes. It is useful for cleaning contact lists before outreach or import.

SUBSCRIPTION PLANS

Choose a quota that matches the workload.

Plans are shown for reference. Live checkout opens after an API route has an upstream URL.

WALLET-ACCESS

Pay-as-you-go access

$0.00 / month

Wallet credits per call
$0.0050 / call overage
120 req/min

INTEGRATION PATH

From first request to production.

Start with a Dakidarts key, call the gateway, then monitor usage from the dashboard.

Create a Dakidarts key

Choose the API scope, then copy the key into your server environment.

Call the gateway

Send requests to https://api.dakidarts.com/checky-email with your key and JSON body.

Watch usage

Track calls, latency and spend from the API dashboard and wallet.

ENDPOINT REFERENCE

Endpoint reference & metered costs.

These routes include contracts imported from the product implementation. 0 of 5 endpoints have an upstream URL configured. Other routes return 503 before billing; saved examples are previews only. Configure an upstream URL in API Studio to enable those routes.

GROUP / 01

Operations

Operations endpoints sourced from the Checky Email Verification API implementation.

2 endpoints

GET /status Ping SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Returns Checky Email service health.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 22), handler ping, in the emval source repository. The source does not declare an API version (Unversioned). The handler and parameter names are transcribed from the source; any sample request values are illustrative, not captured upstream output.

Execution note: This is a source contract, not a live response. Examples are illustrative; requests need a configured upstream to execute.

Source contract imported from emval/app.py. Handler: ping.

SAMPLE RESPONSE

{
  "status": "API is online"
}

QUICK CURL

curl -X GET https://api.dakidarts.com/checky-email/status -H 'X-API-Key: dk_live_...' -H 'Accept: application/json'

POST /status Ping SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Returns Checky Email service health.

Source implementation

Execution note: This is a source contract, not a live response. Examples are illustrative; requests need a configured upstream to execute.

Source contract imported from emval/app.py. Handler: ping.

SAMPLE RESPONSE

{
  "status": "API is online"
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-email/status -H 'X-API-Key: dk_live_...' -H 'Accept: application/json'

GROUP / 02

Email validation

Email validation endpoints sourced from the Checky Email Verification API implementation.

3 endpoints

POST /validate Validate Email Endpoint SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Validates email syntax and domain information.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from POST uses app.py (line 29, validate_email_endpoint); GET uses app.py (line 102, validate_email_get) in the emval source repository. The source does not declare an API version (Unversioned). The parameter table is the handler-backed contract; response fields are shown as a shape when the repository does not provide a trustworthy concrete sample. No live upstream request was made.

Execution note: This route remains source-contract-only until a real upstream is configured.

Source contract imported from emval/app.py. Handler: validate_email_endpoint.

PARAMETERS

Name	In	Type	Required	Description
`email`	body	string	Yes	Email address to validate.

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "requestID": {
      "type": "string",
      "format": "uuid"
    },
    "timestamp": {
      "type": "string",
      "format": "date-time"
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-email/validate -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"email": "example"}'

GET /validate Validate Email Endpoint SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Validates email syntax and domain information.

Source implementation

Execution note: This route remains source-contract-only until a real upstream is configured.

Source contract imported from emval/app.py. Handler: validate_email_get.

PARAMETERS

Name	In	Type	Required	Description
`email`	query	string	Yes	Email address to validate.

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "requestID": {
      "type": "string",
      "format": "uuid"
    },
    "timestamp": {
      "type": "string",
      "format": "date-time"
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X GET 'https://api.dakidarts.com/checky-email/validate?email=dev%40example.com' -H 'X-API-Key: dk_live_...' -H 'Accept: application/json'

POST /extract Extract Emails Endpoint SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Extracts email addresses from text.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 173), handler extract_emails_endpoint, in the emval source repository. The source does not declare an API version (Unversioned). The parameter table is the handler-backed contract; response fields are shown as a shape when the repository does not provide a trustworthy concrete sample. No live upstream request was made.

Execution note: This route remains source-contract-only until a real upstream is configured.

Source contract imported from emval/app.py. Handler: extract_emails_endpoint.

PARAMETERS

Name	In	Type	Required	Description
`text`	body	string	Yes	Text from which email addresses should be extracted.

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "requestID": {
      "type": "string",
      "format": "uuid"
    },
    "timestamp": {
      "type": "string",
      "format": "date-time"
    },
    "validation_results": {
      "type": "object",
      "additionalProperties": true
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-email/extract -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"text": "example"}'

INTERACTIVE SANDBOX

Explore a response before you integrate.

Edit a JSON request to validate its syntax and preview the published sample response. This stays in your browser; it never calls the live API or uses credits.

The preview checks JSON syntax and shows the saved example response; it does not execute request values.

MOCK RESPONSE

TYPESCRIPT CONTRACT

INTEGRATION SDK

Use the product where it lives.

These are integration templates, not runnable sample calls. Configure an endpoint upstream in API Studio, then replace the placeholder path. Saved samples stay preview-only.

REST/JSON

# Replace with a connected GET route and include any required parameters.
curl -X GET "https://api.dakidarts.com/checky-email/v1/your-connected-endpoint" \
  -H "X-API-Key: dk_live_..." \
  -H "Accept: application/json"

# Replace with a connected GET route and include any required parameters.
import requests

headers = {"X-API-Key": "dk_live_..."}
response = requests.get("https://api.dakidarts.com/checky-email/v1/your-connected-endpoint", headers=headers)
print(response.json())

// Replace with a connected GET route and include any required parameters.
const res = await fetch("https://api.dakidarts.com/checky-email/v1/your-connected-endpoint", {
  headers: { "X-API-Key": "dk_live_..." }
});
const data = await res.json();
console.log(data);

<?php
// Replace with a connected GET route and include any required parameters.
$ch = curl_init("https://api.dakidarts.com/checky-email/v1/your-connected-endpoint");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["X-API-Key: dk_live_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);

Explore more Identity and adjacent APIs.

Full catalog

Checky Email Verification API

Call Checky Email Verification API through the Dakidarts gateway.

One key, one gateway

Metered by the call

Observable by default

Also available through RapidAPI.

Built to disappear into the product.

Improve contact quality in signup and lead-capture flows

Validate individual addresses with GET or POST

Extract multiple candidate addresses from submitted text

The shape of the surface.

Answers before you integrate.

Choose a quota that matches the workload.

Pay-as-you-go access

From first request to production.

Create a Dakidarts key

Call the gateway

Watch usage

Endpoint reference & metered costs.

Operations

Source implementation

Source implementation

Email validation

Source implementation

Source implementation

Source implementation

Explore a response before you integrate.

Use the product where it lives.

Explore more Identity and adjacent APIs.

Checky — Verify Phone Number API