CSV Exports
Download your leads as a CSV: choose the sources and exactly which fields go in the file.
Queue a CSV export of a website's leads from your own code. The file is built in the background and emailed; the call itself does not return the file. Authenticated with ?privateKey=YOUR_KEY (see Authentication).
| POST | /v3/leads/export | Export leads to CSV |
POST
/v3/leads/exportTry:
Request body
Website IdWebsite id (24 hex characters) from list_websites.
Date FromStart of the range (last visit date). Accepts YYYY-MM-DD, MM/DD/YYYY, ISO 8601 or epoch milliseconds.
Date ToEnd of the range, inclusive. Same formats as dateFrom.
curl -X POST "https://rest-dash.revealid.xyz/v3/leads/export?privateKey=YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "websiteId": "64b7f0a1c2d3e4f5a6b7c8d9", "dateFrom": "2026-10-01", "dateTo": "2026-10-30"}'Response
Press Send request to try it with sample data.
What each field accepts
| Field | Type | Limits and format | Accepted values |
|---|---|---|---|
| websiteId* | string | — | any |
| dateFrom* | string | — | any |
| dateTo* | string | — | any |
Use case: A monthly export
POST /v3/leads/export with the month as dateFrom/dateTo (matched on each lead's last visit). It answers status: "queued" with a job (id, stage, progress, rowCount, fileName, expiresAt); the download link is emailed to you and the file stays under CSV Exports for 30 days. Each finished export uses one of your plan's CSV downloads and fails when none are left. To read leads in your code instead, use GET /v3/leads.