[POST] - New Contact Details Job

  • Updated

Use the New Contact Job endpoint to submit a bulk of New Contact Details queries. It creates an asynchronous job on InsideView servers. See Using the Bulk APIs for more details.

Endpoint

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

Request

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).

Query Parameters

Parameter Name Type Required Description
retrieveCompanyDetails Boolean No If set to True retrieve company details  along with contact
webhook String No URL to receive Job status

 

Request Body

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

Example Input Data

Call the [POST] - Contact List and get the id values from the response. From there, use the accessToken that is issued to the same client_id.
Note: This is an example, id values are client specific. 
84OKnj1c07bdsDwj8_O4ZHqpHFcAIJQVdw1sczYgi_P3IDQTZ-e_DGORXj4V5MhD
NZ30nmuF51Z7fsFoZ149FDMYzsVPFZhftV_NPzgl8Kx-KHLSPu0_mSiSvzdLxnMQ
1WhHImR7pXLvHsM8ffnIoWK5s_zgcOqCZyhUv7NmkRgC44OZZGkhYVcaFopQQfhk
RtAQCfBKDqHDOghtle5Wmw_1r-D_OQtmLSMgIfQSAbcvEnQVZaGopyLYZEvHNRNU
d19oY8bwn5MwYVdk07mKNGf-uSGSYMWWhIuZASFECKaLMaIkPt2FgVlhHMIfQlbq

Responses

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

An HTTP 200 status means the data have been accepted and a job have been queued.

Type: application/json

Schema

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "id": "/",
  "type": "object",
  "properties": {
    "jobId": {
      "id": "jobId",
      "type": "string"
    },
    "status": {
      "id": "status",
      "type": "string"
    },
    "type": {
      "id": "type",
      "type": "string"
    }
  }
}

Example

{
  "jobId": "lnjkd7ie0hblp1k58e5q",
  "status": "accepted",
  "type": "targetContactDetails"
}

Type: application/xml

Schema

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">

    <xs:element name="BulkJobStatus" type="BulkJobStatusDTO"/>

    <xs:complexType name="BulkJobStatusDTO">
        <xs:sequence>
            <xs:element name="jobId" type="xs:string" />
            <xs:element name="status" type="xs:string" />
            <xs:element name="type" type="xs:string" />     
        </xs:sequence>
    </xs:complexType>
</xs:schema>

Example

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<BulkJobStatus>
    <jobId>81g8d74jjo8s4grarkii</jobId>
    <status>accepted</status>
    <type>targetContactDetails</type>
</BulkJobStatus>

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 is not valid, please refer to the API documentation.

HTTP 429

Request is throttled.

 

Was this article helpful?

0 out of 0 found this helpful