leadcapture.now
Join waitlist

CSV & API export

Download structured leads for a spreadsheet handoff, or pull JSON into Claude, Clay, and your outreach stack with the export API.

CSV export

From ops screens, download a CSV for the leads you are viewing. Exports include structured fields, conversation context, LinkedIn connect notes, and optional enrichment results when you have run lookups—ready for sheets or a one-off handoff.

No enrichment required

You do not need to enrich in the app to export useful data. Many early-access users export structured captures directly and enrich in Clay, Apollo, or your CRM, or paste CSV into Claude for follow-up drafts.

Use CSV when you want a snapshot for a specific day or filter. Use the API when your systems should pull continuously.

Export API

Authenticated systems can read reviewed leads as JSON from /api/leads. Pass your export API key as a Bearer token.

By default, the API returns leads captured on today (workspace timezone). To pull a specific event day, add a date query parameter in YYYY-MM-DD format—the same date you pick on the ops dashboard.

# Today's leads (date optional)
curl "https://leadcapture.now/api/leads" \
  -H "Authorization: Bearer YOUR_EXPORT_API_KEY"

# Leads from a specific capture date
curl "https://leadcapture.now/api/leads?date=YYYY-MM-DD" \
  -H "Authorization: Bearer YOUR_EXPORT_API_KEY"

Replace YOUR_EXPORT_API_KEY with a key from Settings, and YYYY-MM-DD with the day you want (for example, 2026-03-15 for March 15, 2026).

Responses include contact fields, enrichment metadata (enrichmentStatus, enrichmentSource, enrichedAt), and the same structured context reps captured on the floor. JSON is especially easy for Claude to parse for prioritization and follow-up drafting.

Common integrations

The export API is standard HTTP with Bearer auth—no vendor-specific connector required. Typical setups:

  • Claude — call /api/leads, paste or pipe the JSON into a chat, or fetch on a schedule from Claude Code or a private project. Great for drafting follow-ups from booth context.
  • Clay — import CSV, send API results to a Clay table webhook, or connect Clay as your in-app enrichment provider under Workspace settings.
  • CRM & outreach — Apollo, HubSpot, Salesforce, or your stack via CSV import or automation.
  • Automation — Zapier, Make, or a cron script hits /api/leads with your API key and forwards results wherever you need them.

Security

Treat API keys like passwords. Use them in private automation or local scripts—not in public Claude chats or shared docs.

API keys

Ops users and workspace admins create export API keys under Settings → API keys. Treat keys like passwords—rotate them if someone leaves the team or a key is exposed.