zintara.io

Integrations · Practical guide

Zintara contact import API: preview, map and monitor the job

Use the multipart CSV import flow and inspect the asynchronous job outcome before treating contacts as ready.

Reviewed · Examples are illustrative

Who this helps: Operators connecting and reconciling outreach systems.

Define the decision

The reviewed import routes sit under /api/leads/imports and require the corresponding lead scope. Preview accepts a file part; creation accepts a CSV file plus options such as mapping, deduplicate, skipInvalid, enrichOnImport and listName.

Work through the procedure

  1. Prepare a small synthetic CSV with explicit column names.
  2. POST the file to /api/leads/imports/preview and inspect the returned preview.
  3. Submit an approved mapping and options to POST /api/leads/imports.
  4. Save the returned job identity and poll its job and events routes with a read-capable key.
  5. Reconcile imported, skipped and failed rows before enrollment.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Preview route: POST /api/leads/imports/preview
Create route: POST /api/leads/imports
Monitor: GET /api/leads/imports/{jobId}
Events: GET /api/leads/imports/{jobId}/events
202 Accepted means processing was accepted, not that every row succeeded.

Read the result

The mapping must follow the actual preview and application-supported field names. Preserve the source file identity and selected options in the integration record so a failed batch can be explained.

Check before moving on

  1. Use multipart field name file and a .csv filename.
  2. Check the deployment upload limit rather than assuming an unlimited payload.

Limits and next action

Do not blindly repeat a timed-out creation request. Determine whether a job was already created, and keep suppression and contact eligibility separate from successful import.

Source: Zintara implementation and product context

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow