Skip to content
Docs

Export Leads

Start a CSV export of your leads as a background job.

POST/api/v1/leads/export

Requires an API key with the read scope.

Builds a CSV of up to 100,000 leads, newest first, in the background. The call returns a 202 with a lead_export job. When the job is completed, its result carries rows, downloadUrl and expiresInSeconds. Fetch the file with Download Lead Export using the same API key. The file is kept for one hour.

Custom fields become extra columns. Spreadsheet formulas in values are neutralised.

Body Parameters#

searchstringbody
Match email, first name, last name or company.
tagsstringbody
Comma separated tag names; a lead must carry all of them.

Response#

dataobject

The job (type lead_export, status pending). Once completed, result is { "rows": 4210, "downloadUrl": "/api/v1/leads/export/{job_id}/download", "expiresInSeconds": 3600 }.

Errors#

StatusDescription
401Missing, invalid, revoked or expired API key
403API key does not have the required scope: read

Rate Limit#

  • 100 requests per minute, shared by every bulk call in your workspace. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (unix epoch seconds) and X-RateLimit-Bucket (bulk).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 4, 2026