Get a contact import
Changed onRetrieve a single contact import — the same row /v1/imports lists for it.
Required scope: contacts_read
Request
- Base URLhttps://api.privy.com/v1
- AuthHTTP bearer
Path parameters
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.
Headers
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.
Response
The import.
Example response
{
"data": {
"id": "im_k2R5m8Q",
"channel": "email",
"source": "csv",
"status": "partial",
"review_status": "approved",
"requested_by": "Rita Requester"
}
}Changes
- warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
forbiddenenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status - warning
added the new
segment_builder_requiredenum value to the/response property for the response status
- warning
- info
endpoint added
- info