Build with
SearchLeads.

Your first requestCopy Anchor Link

Create an API key with the search scope, then send a small request to find matching prospects. Returned people records use export credits; each page is an API call.

The examples on this page already use this environment's API host. Replace only the API-key placeholder with the full key shown when you create it.

API keys, search IDs, permissions, credits, and datasets belong to one environment. Keep every call in a workflow on the same API base.

For an AI client, use Copy for AI, the complete text guide, or the public JSON input contract. These contain all public field contracts without requiring JavaScript. Authenticated capabilities remain authoritative for the key owner's current access.

curl -X POST "https://ttzqldekaizydrdmirpn.supabase.co/functions/v1/people-search" \
  -H "Content-Type: application/json" \
  -H "x-searchleads-api-key: sl_live_your_full_api_key_here" \
  -d '{
    "searchType": "people",
    "textFilters": { "contact.keyword": "sales" },
    "page": 0,
    "size": 1
  }'

The response contains results.content, results.totalElements, and a search_id for asynchronous exports.

Next stepsCopy Anchor Link

• Authentication covers API keys and safe storage.
• Search describes request fields, examples, and pagination.
• Filters shows how to discover valid filter values.
• Capabilities returns the current limits, access, and field catalog for your key.
• MCP connects compatible AI clients to the hosted server.

Your account's live capabilities response is authoritative for enabled search types, field access, current limits, and export options.

• Saved searches and sharing creates reusable definitions and signed-in, expiring share links through REST or MCP.