Public API - Quick Reference

The Public API lets you pull the same verified token-project leads you see on the Leads page. Use it to feed CRMs, internal tools, or data pipelines. For key management and quotas, see API Keys and for CRM patterns see Connect LeadGenCrypto to CRM.

Public endpoint, private data

The API is “public” only in the sense that it’s reachable over the internet.
Your leads are not public — every request requires your API key, and responses contain only leads allocated to your account.

Base URL

https://api.leadgencrypto.com/api

Authentication

Pass your API key as a query parameter:

apikey=YOUR_API_KEY

• Keep keys in environment variables or a secrets manager, not in source control.
• Rotate the key from the API Keys page if it is ever exposed.

Treat the API key like a password

Anyone with your key can read your leads. Do not share it in screenshots, repos, or chat logs.

---

Endpoints

There are two read-only endpoints. Both return the same lead fields; they differ only in how they select rows.

viewRecentLeads - last 24 hours

Fetch leads assigned to your account in the last 24 hours.

GET URL

https://api.leadgencrypto.com/api?module=lead&action=viewRecentLeads&apikey=YOUR_API_KEY

cURL

curl -i "https://api.leadgencrypto.com/api?module=lead&action=viewRecentLeads&apikey=YOUR_API_KEY"

Use this for cron-style jobs that run at the minimum interval allowed by your plan.

---

viewLatestLeads - most recent with limit

Fetch the most recent leads from your account up to limit.

GET URL

https://api.leadgencrypto.com/api?module=lead&action=viewLatestLeads&limit=100&apikey=YOUR_API_KEY

cURL

curl -i "https://api.leadgencrypto.com/api?module=lead&action=viewLatestLeads&limit=100&apikey=YOUR_API_KEY"

Notes:

• limit is optional but recommended so you control batch size.
• The platform validates limit against your Max leads per call. If it is too high, the API may clamp it or return an error such as limit exceeds plan maximum. Check your quotas on the API Keys page and keep limit at or below that value.

Use this for incremental syncs into a CRM or data warehouse.

---

Query parameters

Name	Type	Required	Example	Applies to	Notes
module	string	yes	lead	both	Resource group. Currently only lead is used.
action	string	yes	viewRecentLeads or viewLatestLeads	both	Selects which endpoint to call.
limit	int	no	100	viewLatestLeads only	Max rows to return. Subject to per-plan cap.
apikey	string	yes	YOUR_API_KEY	both	Workspace API key from the app.

---

Rate limits

Typical defaults:

Plan	Requests / second	Daily cap	Minimum interval between calls	Max leads per call (viewLatestLeads)
Free	1	~24/day	120 s	Up to 100
Paid	1	~1500/day	60 s	Up to 1000

• Your actual values can differ by plan and may be tuned by admins.
• The API Keys page in the app always shows the limits that apply to your account right now.

Stay within your quotas

Schedule calls at or above the minimum interval, keep limit conservative, and back off if you see rate_limited or similar errors. This keeps your integration stable and avoids dropped jobs.

---

Response shape

All endpoints return JSON with status, message, and a result array.

• On success, status is a success string, message is usually "OK", and result is an array of lead objects.
• When nothing qualifies, result is an empty array.
• On errors, status is an error string and message explains what went wrong.

Success example

{
  "status": "success",
  "message": "OK",
  "result": [
    {
      "createdAt": "2025-10-12T09:41:33Z",
      "website": "https://project.example",
      "tokenAddress": "0xabc123...",
      "blockchain": "Base",
      "tokenSymbol": "EXMPL",
      "tokenName": "Example",
      "tokenUrl": "https://etherscan.io/token/0xabc123...",
      "email1": "contact@project.example",
      "email2": null,
      "telegram": "https://t.me/example"
    }
  ]
}

Empty result example

{
  "status": "success",
  "message": "OK",
  "result": []
}

Invalid limit example

{
  "status": "error",
  "message": "limit exceeds plan maximum",
  "result": []
}

Invalid or missing API key

{
  "status": "error",
  "message": "invalid api key",
  "result": []
}

Rate limited

{
  "status": "error",
  "message": "rate_limited",
  "result": []
}

---

Integration tips

• Prefer viewRecentLeads for scheduled jobs (for example, every 2 hours on a paid plan) and viewLatestLeads with a moderate limit for catch-up or manual runs.
• Treat website, tokenUrl, tokenAddress, and the primary email as identity keys in your CRM to avoid duplicates. See Connect LeadGenCrypto to CRM.
• Duplicate suppression inside LeadGenCrypto still applies: the API will not return the same lead to your account again if it has the same primary email or token URL as a lead already delivered. Use Filters & Exceptions to suppress contacts from your own lists.
• Combine this page with API Keys for key management and Troubleshooting & Tips if you hit invalid api key, rate_limited, or empty responses.