[POST] - Contact Details Job

  • Updated

Use the Contact Details Job endpoint to submit a bulk of Contact Details queries (allows retrieving contact details by id). It creates an asynchronous job on InsideView servers. See Using the bulk APIs for more details.

The contact ids can be obtained either through the Data API Contact Search or through the Enrich API Enrich (or its bulk version).


POST https://api.insideview.com/api/v1/contact/job


HTTP Headers

Header Name Type Required Description
accessToken String Yes Valid access token.
See Authentication and Authorization Overview for more details.
Accept String No Selects the response's content type.  
Valid values are application/json and application/xml (default).
Content-Type String Yes Input content type.
Valid values are application/octet-stream and text/plain  

Query Parameters

Parameter Name Type Required Description
webhook String No URL for receiving Job status



Request Body

The request body should contain a list of contact ids, either separated with commas or a new line.  The request can contain up to 10,000 contact ids.  

Example input data (1)


Example input data (2)



Here are the major responses the API may return.

This API returns email validation status in a .CSV response file, which you can download.

For details on the errors, see API Error Codes.

HTTP 200

Returns either a JSON or XML data structure depending on the request Accept header. 

application/json Example


application/xml Example

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

HTTP 400

An HTTP 400 error code may have several causes:

  • Validation of input data failed
  • Insufficient transaction quota available
  • Too many job submitted to the processing queue
  • etc.

HTTP 401

Unauthorized Error - Cannot use API's without setting a valid accessToken in header.

HTTP 405

Method Not Allowed - Your are not allowed to access this API.

HTTP 415

The Content-Type mandatory header is not provided.

HTTP 429

Request is throttled.


Was this article helpful?

0 out of 0 found this helpful