Leads

Create a leads import from CSV data

Creates a draft leads import and returns its id, the guessed column matching, and a configuration_url. This call does not import anything: a person must open that URL in a browser and complete the mapping step before any lead is created. It is intended for clients that can hand off to a browser session, not for unattended automation. csv_data must be sent in the request body; it is rejected in the query string, where it would reach access logs verbatim.

post/leads-imports

Request

  • Base URL: https://api.hunter.io/v2
  • URL: https://api.hunter.io/v2/leads-imports
  • Auth: one of:
    • API key in query parameter api_key
    • API key in header X-API-KEY
    • HTTP bearer

Request body

api_keystring
csv_datastring required

The CSV content. Comma and semicolon separators are both detected. The server rejects anything over 10 MB once encoded, which is a byte limit and so cannot be expressed as maxLength. Over 100,000 rows is rejected. Send a large CSV as JSON: percent encoding can treble a form-encoded body, which the proxy rejects at 25 MB before the endpoint sees it.

leads_list_idinteger

Identifier of the static list the leads should land in. Must belong to your team. Omit it to pick a destination on the configuration page.

file_namestring

Name shown for this import in the imports history. A longer name is truncated rather than rejected, so no maxLength is declared.

Response

Create a leads import from CSV data.

GenericResourceResponse required

Generic envelope for V2 resource operations whose detailed schema is not yet in the contract.

Changes

No recorded changes to this operation across all 1 revision of this API.