← API network IDENTITY / PHONE / VALIDATION / INTAKE

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

Checky — Verify Phone Number API

Phone-number validation and normalization with number type, carrier, geographic description and time-zone metadata, plus batch verification and text extraction.

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

Direct PlatformCH

api.dakidarts.comUnversionedGeneral Availability25ms p959 documented endpoints

DIRECT NATIVE API

Call Checky — Verify Phone Number API through the Dakidarts gateway.

0 of 9 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-phone

AuthenticationX-API-Key: dk_live_...

Default reference pathGET /verify

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.

Normalize submitted numbers for intake flows

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

Verify lists without failing the whole batch for one invalid entry

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

Extract phone numbers from text with a country context

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.

01Number validity, region and type checks

02Carrier, geographic description and time-zone lookups

03Single, batch and text-finder workflows

FAQ

Answers before you integrate.

Access, billing and integration details for Checky — Verify Phone Number API.

What does phone verification do? +

It validates and normalizes user-supplied phone numbers for cleaner intake flows.

Where can I use it? +

Sign-up forms, CRM intake and back-office contact workflows.

Does it guarantee the number belongs to a person? +

No. It screens format and validity signals; it does not prove ownership.

How do I get access? +

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

Does it support international numbers? +

It handles common international formats supported by the validation surface.

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-phone 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 9 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 — Verify Phone Number API implementation.

2 endpoints

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

Returns Checky Phone service health.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 18), handler ping, in the checky 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 checky/app.py. Handler: ping.

SAMPLE RESPONSE

{
  "status": "API is online"
}

QUICK CURL

curl -X GET https://api.dakidarts.com/checky-phone/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 Phone 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 checky/app.py. Handler: ping.

SAMPLE RESPONSE

{
  "status": "API is online"
}

QUICK CURL

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

GROUP / 02

Phone verification

Phone verification endpoints sourced from the Checky — Verify Phone Number API implementation.

7 endpoints

GET /verify Verify Phone SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Validates a phone number and returns its normalized number and type.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 53), handler verify_phone, in the checky 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 checky/app.py. Handler: verify_phone.

PARAMETERS

Name	In	Type	Required	Description
`phone`	query	string	Yes	Phone number to validate or look up; include the international prefix when available.
`country`	query	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	query	string	No	Language/locale used for localized phone metadata.

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "valid": {
      "type": "boolean"
    },
    "carrier": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "country": {
      "type": "integer"
    },
    "location": {
      "type": "object",
      "additionalProperties": true
    },
    "timezone": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "phone_type": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "phone_number": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "emergency_number": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "country_mobile_code": {
      "type": "integer"
    },
    "can_be_dialled_internationally": {
      "description": "Dynamic source value; no concrete response example is published."
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X GET 'https://api.dakidarts.com/checky-phone/verify?lang=en' -H 'X-API-Key: dk_live_...' -H 'Accept: application/json'

POST /verify/batch Verify Phone Batch SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Validates a list of phone numbers and returns independent results.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 110), handler verify_phone_batch, in the checky 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 checky/app.py. Handler: verify_phone_batch.

PARAMETERS

Name	In	Type	Required	Description
`phone`	body	array	Yes	Array of phone numbers to process.
`country`	body	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	body	string	No	Language/locale used for localized phone metadata.

SAMPLE REQUEST

{
  "lang": "en",
  "phone": [
    "+12025550123",
    "+12025550124"
  ],
  "country": "US"
}

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {},
        "additionalProperties": true
      }
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-phone/verify/batch -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"lang": "en", "phone": ["+12025550123", "+12025550124"], "country": "US"}'

POST /verify/post Verify Phone Post SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Validates one phone number from a JSON request body.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 183), handler verify_phone_post, in the checky 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 checky/app.py. Handler: verify_phone_post.

PARAMETERS

Name	In	Type	Required	Description
`phone`	body	string	Yes	Phone number to validate or look up; include the international prefix when available.
`country`	body	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	body	string	No	Language/locale used for localized phone metadata.

SAMPLE REQUEST

{
  "lang": "en",
  "phone": "+12025550123",
  "country": "US"
}

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "carrier": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "country": {
      "type": "integer"
    },
    "location": {
      "type": "object",
      "additionalProperties": true
    },
    "timezone": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "phone_type": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "phone_number": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "emergency_number": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "country_mobile_code": {
      "type": "integer"
    },
    "can_be_dialled_internationally": {
      "description": "Dynamic source value; no concrete response example is published."
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-phone/verify/post -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"lang": "en", "phone": "+12025550123", "country": "US"}'

GET /carrier Get Carrier SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Looks up carrier, geographic description, and time zones for a phone number.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 239), handler get_carrier, in the checky 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 checky/app.py. Handler: get_carrier.

PARAMETERS

Name	In	Type	Required	Description
`phone`	query	string	Yes	Phone number to validate or look up; include the international prefix when available.
`country`	query	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	query	string	No	Language/locale used for localized phone metadata.

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "carrier": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "location": {
      "type": "object",
      "additionalProperties": true
    },
    "country_code": {
      "type": "integer"
    },
    "phone_number": {
      "description": "Dynamic source value; no concrete response example is published."
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X GET 'https://api.dakidarts.com/checky-phone/carrier?lang=en' -H 'X-API-Key: dk_live_...' -H 'Accept: application/json'

POST /carrier/batch Get Carrier Batch SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Looks up carrier information for a list of phone numbers.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 271), handler get_carrier_batch, in the checky 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 checky/app.py. Handler: get_carrier_batch.

PARAMETERS

Name	In	Type	Required	Description
`phone`	body	array	Yes	Array of phone numbers to process.
`country`	body	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	body	string	No	Language/locale used for localized phone metadata.

SAMPLE REQUEST

{
  "lang": "en",
  "phone": [
    "+12025550123",
    "+12025550124"
  ],
  "country": "US"
}

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {},
        "additionalProperties": true
      }
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-phone/carrier/batch -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"lang": "en", "phone": ["+12025550123", "+12025550124"], "country": "US"}'

POST /carrier/post Get Carrier Post SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Looks up carrier information from a JSON request body.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 327), handler get_carrier_post, in the checky 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 checky/app.py. Handler: get_carrier_post.

PARAMETERS

Name	In	Type	Required	Description
`phone`	body	string	Yes	Phone number to validate or look up; include the international prefix when available.
`country`	body	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.
`lang`	body	string	No	Language/locale used for localized phone metadata.

SAMPLE REQUEST

{
  "lang": "en",
  "phone": "+12025550123",
  "country": "US"
}

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "carrier": {
      "description": "Dynamic source value; no concrete response example is published."
    },
    "location": {
      "type": "object",
      "additionalProperties": true
    },
    "country_code": {
      "type": "integer"
    },
    "phone_number": {
      "description": "Dynamic source value; no concrete response example is published."
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-phone/carrier/post -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"lang": "en", "phone": "+12025550123", "country": "US"}'

POST /finder Find Phone Numbers SOURCE CONTRACT — UPSTREAM NEEDED $0.0050 / call / 120 rpm Upstream needed

Finds phone numbers in text using the supplied country context.

Source implementation

This repository does not publish a separate endpoint guide for this route. The contract is transcribed from app.py (line 380), handler find_phone_numbers, in the checky 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 checky/app.py. Handler: find_phone_numbers.

PARAMETERS

Name	In	Type	Required	Description
`text`	body	string	Yes	Text in which phone numbers should be detected.
`country`	body	string	Yes	ISO 3166-1 alpha-2 region code used to parse a national-format phone number.

SAMPLE REQUEST

{
  "text": "Call the demo line at +1 202-555-0123.",
  "country": "US"
}

RESPONSE SHAPE / NO VERIFIED SAMPLE

{
  "type": "object",
  "properties": {
    "error": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "phone_numbers": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {},
        "additionalProperties": true
      }
    }
  },
  "additionalProperties": true
}

QUICK CURL

curl -X POST https://api.dakidarts.com/checky-phone/finder -H 'X-API-Key: dk_live_...' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"text": "Call the demo line at +1 202-555-0123.", "country": "US"}'

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-phone/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-phone/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-phone/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-phone/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 — Verify Phone Number API

Call Checky — Verify Phone Number 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.

Normalize submitted numbers for intake flows

Verify lists without failing the whole batch for one invalid entry

Extract phone numbers from text with a country context

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

Phone verification

Source implementation

Source implementation

Source implementation

Source implementation

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 Email Verification API