LastDatabase API Documentation

The LastDatabase API provides programmatic access to lead-data search, B2B contact discovery and unlocking, email verification, phone verification, WhatsApp number verification, Telegram number verification, account credits and API usage information.

A single active customer API key can authenticate supported LastDatabase API services. You do not need a separate API key for lead search, email verification, phone verification, WhatsApp verification and Telegram verification.

API request capacity is separate from product consumption. Your API plan controls technical request limits and API-key capacity. Product packages determine lead-record allowance, verification credits and messaging-verification wallet funds.

Quick Start

1. Create an API key

Sign in to your customer account and open API Management. Generate an API key for your application and store it securely on your server.

2. Send the Bearer token

Authorization: Bearer YOUR_API_KEY
Accept: application/json

3. Test a non-destructive search

curl -X GET \
  "https://lastdatabase.com/api/integrations/v1/people/search?country=USA&industry=technology&limit=5" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

People Search is a discovery operation. Email addresses returned by this endpoint are masked. Use People Unlock when you intentionally want to unlock an individual B2B contact.

Authentication

Protected API endpoints use HTTP Bearer authentication. Include your active API key in the Authorization request header.

Authorization: Bearer YOUR_API_KEY

Missing credentials return HTTP 401 Unauthorized with a missing-token response. An invalid or disabled API key also returns HTTP 401.

Each authenticated request counts toward the daily request allowance attached to the API key. When the key reaches its daily limit, the API returns HTTP 429 Too Many Requests.

See the complete API Authentication guide for credential storage, key rotation, rate limits and production security practices.

Endpoint Directory

Lead Data Search API

The general lead-search endpoint supports multiple LastDatabase data inventories through the type query parameter.

GET https://lastdatabase.com/api/leads/search

Supported search criteria include country, city, industry and keyword where applicable. The result limit is bounded by the endpoint.

curl -X GET \
  "https://lastdatabase.com/api/leads/search?type=email&country=USA&industry=technology&keyword=CEO&limit=10" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Response envelope

{
  "status": true,
  "type": "email",
  "count": 10,
  "data": [
    ...
  ]
}

The data fields depend on the selected inventory type. Applications should tolerate nullable or unavailable fields instead of assuming that every record contains every possible attribute.

For detailed filtering and implementation guidance, see API Search and Filtering.

People Search and Unlock API

The integration People API separates discovery from consumption. Search returns B2B contacts with masked email addresses. Unlock is a separate operation.

Search people

GET /api/integrations/v1/people/search

At least one of keyword, country, city or industry must contain a value.

curl -X GET \
  "https://lastdatabase.com/api/integrations/v1/people/search?country=USA&industry=technology&limit=5" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

The response can include record ID, first name, last name, masked email, job title, seniority, company, company website, LinkedIn URL, industry, country, state, city, postal code, employee size, revenue and technology where those fields are available.

Unlock a person

POST /api/integrations/v1/people/unlock

{
  "lead_id": 26515564
}

lead_id is required and must be a positive integer. Unlocking uses the existing LastDatabase customer subscription, suppression and verification workflow. Search itself should be used for discovery before deciding which record to unlock.

Email Verification API

POST /api/integrations/v1/email/verify

The request accepts one required email value. It must be a syntactically valid RFC email address and cannot exceed 254 characters.

curl -X POST \
  "https://lastdatabase.com/api/integrations/v1/email/verify" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "user@example.com"
  }'

A successful response includes status, type, the normalized identifier and the verification result.

See the Email Verifier documentation for additional verification concepts and result interpretation.

Phone Verification API

POST /api/integrations/v1/phone/verify

curl -X POST \
  "https://lastdatabase.com/api/integrations/v1/phone/verify" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+8801712345678",
    "country": "BD",
    "idempotency_key": "550e8400-e29b-41d4-a716-446655440000"
  }'

Phone Verification uses the same verification-credit system as the customer dashboard. The API controller does not independently debit a second set of credits.

HTTP 402 can be returned when verification credits are insufficient.

See the Phone Verifier documentation for additional guidance.

WhatsApp Number Verification API

POST /api/integrations/v1/whatsapp/verify

WhatsApp verification is a bulk asynchronous operation. Submit an array of phone numbers and a unique request UUID.

The current customer price is $0.01 per billable number. The amount is reserved from the customer's LastDatabase messaging wallet when the job is created and finalized according to the verification workflow.

curl -X POST \
  "https://lastdatabase.com/api/integrations/v1/whatsapp/verify" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "numbers": [
      "+15550000001",
      "+15550000002"
    ],
    "request_uuid": "550e8400-e29b-41d4-a716-446655440001"
  }'

Accepted response

Successful job creation returns HTTP 202 Accepted. The response includes the service, job ID, request UUID, job status, total numbers, billable numbers, price per number, total amount and creation timestamp.

{
  "status": true,
  "service": "whatsapp",
  "job": {
    "id": 123,
    "request_uuid": "550e8400-e29b-41d4-a716-446655440001",
    "status": "pending",
    "total_numbers": 2001,
    "billable_numbers": 2001,
    "price_per_number_cents": 1,
    "total_amount_cents": 2001,
    "created_at": "2026-09-29T10:00:00+00:00"
  }
}

See the WhatsApp Number Verifier documentation for the broader product workflow.

Telegram Number Verification API

POST /api/integrations/v1/telegram/verify

Telegram verification uses the same bulk submission contract and customer messaging wallet architecture as WhatsApp verification.

{
  "numbers": [
    "+15550000001",
    "+15550000002"
  ],
  "request_uuid": "550e8400-e29b-41d4-a716-446655440002"
}

The same maximum of 10,000 submitted values applies. The effective service minimum is 2,001 valid unique numbers per country, and each country group must satisfy that minimum independently.

Successful job creation returns HTTP 202 Accepted. Insufficient wallet balance can return HTTP 402.

See the Telegram Number Verifier documentation for additional product guidance.

Credits and Usage API

GET /api/integrations/v1/credits

Use this endpoint to inspect remaining lead-subscription records and the authenticated API key's current daily request usage.

curl -X GET \
  "https://lastdatabase.com/api/integrations/v1/credits" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Response structure

{
  "status": true,
  "subscription": {
    "remaining_records": 5000,
    "has_available_records": true
  },
  "api": {
    "daily_limit": 10000,
    "used_today": 125,
    "remaining_today": 9875
  }
}

The values above illustrate the response shape. Your account returns its actual current allowance and API usage.

API Limits vs Product Billing

LastDatabase intentionally separates technical API request limits from commercial product usage.

Current API plans

HTTP Status Codes and Errors

Idempotency and Safe Retries

Operations that can consume product allowance or create asynchronous jobs should be retried carefully.

Phone Verification

Supply a UUID in idempotency_key. When retrying the same logical phone-verification operation, reuse the same key rather than creating a new UUID for every network retry.

WhatsApp and Telegram

Supply a UUID in request_uuid. The messaging submission service uses the request UUID as part of its idempotency workflow. Reuse the same UUID when retrying the same logical submission.

Code Examples

cURL

curl -X GET \
  "https://lastdatabase.com/api/integrations/v1/people/search?country=USA&limit=5" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

PHP

$apiKey = getenv('LASTDATABASE_API_KEY');

$ch = curl_init(
    'https://lastdatabase.com/api/integrations/v1/people/search'
    . '?country=USA&limit=5'
);

curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Accept: application/json',
    ],
]);

$response = curl_exec($ch);

curl_close($ch);

$data = json_decode($response, true);

Python

import os
import requests

api_key = os.environ["LASTDATABASE_API_KEY"]

response = requests.get(
    "https://lastdatabase.com/api/integrations/v1/people/search",
    params={
        "country": "USA",
        "limit": 5,
    },
    headers={
        "Authorization": f"Bearer {api_key}",
        "Accept": "application/json",
    },
    timeout=30,
)

response.raise_for_status()

data = response.json()

Node.js

const apiKey = process.env.LASTDATABASE_API_KEY;

const url = new URL(
  "https://lastdatabase.com/api/integrations/v1/people/search"
);

url.searchParams.set("country", "USA");
url.searchParams.set("limit", "5");

const response = await fetch(url, {
  headers: {
    Authorization: `Bearer ${apiKey}`,
    Accept: "application/json"
  }
});

const data = await response.json();

Security and Production Practices

• Store API keys only in server-side secrets or environment variables.
• Never commit API keys to Git repositories.
• Never expose API keys in browser-side JavaScript.
• Never include real API keys in screenshots, tickets or public documentation.
• Use HTTPS for every production API request.
• Disable credentials that are no longer required.
• Use separate API keys for independent applications when operational separation is useful.
• Validate HTTP status codes before processing response bodies.
• Use idempotency identifiers for operations that require them.

Review the Authentication guide, Compliance, Privacy Policy and Terms before deploying production integrations.

Run the LastDatabase API in Postman

Explore the official LastDatabase API collection in Postman. Use Postman to test authentication, parameters and supported API requests before integrating them into your application.