Imports and prospecting - Sendora

Prospecting operations are split into discovery and mutation. Preview first, inspect the result, then commit only the records you want.

Preview → commit

Start a preview for a lead list.
Poll the preview when the response returns an operation or preview ID.
Inspect counts, duplicates, and source metadata.
Commit the selected preview.
Confirm the resulting job or records.

Do not call a commit endpoint as a substitute for preview. A commit can create leads, consume credits, and change the list.

Imports

curl -X POST "https://api.sendora.ai/api/v1/public/leads/imports" \
  -H "X-API-Key: $SENDORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"leads":[{"email":"jane@example.com","first_name":"Jane"}]}'

For large imports, persist the returned job or import identifier and monitor it instead of assuming every row succeeded.

Enrichment

Enrichment may skip records that are already complete, lack a usable company signal, exceed a cap, or have no result. A successful HTTP response does not necessarily mean every record was enriched. Use small test lists first, store source metadata, and never retry a commit blindly after a timeout.