Skip to main content
GET
Get a contact import

Authorizations

Authorization
string
header
required

Send either an API token or an OAuth access token as Authorization: Bearer <token>. See the Authentication page for details.

Headers

Privy-Account-Id
string

Target a subaccount instead of the main connected account. Pass a subaccount id from get_account's subaccounts list. Only direct subaccounts of the connected account are reachable — omit this for the main account itself.

Path Parameters

id
string
required

The import's prefixed id (im_… for email imports, sim_… for SMS consent imports), as returned by /v1/imports or a contact's import_ids. The prefix selects the record type, so no channel parameter is needed. The part after the prefix is opaque — a numeric id from a Privy dashboard URL is not a valid API id and will 404, with or without the prefix; list imports to find the id.

Response

The import.

data
object

A contact import that created or updated contacts in bulk. Two channels share this shape: email (CSV uploads and connected-provider syncs) and sms (SMS consent imports, a separate review pipeline). Email imports create their contacts when the import is processed — shortly after created_at, before review — and approving the import then applies the pending consent (e.g. never_subscribed to subscribed).

The base row is deliberately slim — the same facts the Privy dashboard's import history shows (id, channel, source, status, review_status, requested_by, counts, created_at).