Articles in this section

See more

[POST] - Contact Lookup Job

Nitin Singh Sisodia
  • Updated
Follow

Use the Contact Lookup Job endpoint to submit a bulk of Contact Lookup queries.  It creates an asynchronous job on InsideView servers.  Refer to Using the bulk API article for more details.

Endpoint

POST https://api.insideview.com/api/v1/target/company/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
webhook String No URL for receiving Job status 

 

Request Body

The request body should contain a list of Contact Lookup queries as CSV data.  The request can contain up to 2,000 lines.  Each line should contain the following fields:

Field Type Required Description
queryId String Yes An identifier for the query
companyID Integer Yes A valid InsideView Company ID
jobLevel String Yes1 A comma separated list of job level IDs.
See API Reference data for a list of IDs.
jobFunction String Yes1 A comma separated list of job function IDs.
See API Reference data for a list of IDs
title String Yes1 Keyword string that will be matched against titles
active Boolean No2 Returns only active or inactive employments.  
Default: true
isEmailRequired Boolean No2 If present and equals to true, returns only records with email address.
isPhoneRequired Boolean No2 If present and equals to true, returns only records with phone number.
peopleCountries String No2 Comma separated list of people country Ids 
peopleStates  String No2 Comma separated list of people states 
peopleCities  String No2 Comma separated list of people cities 
peopleArea  String No2 People area name, ex:Greater San Diego Area
peopleAddress  String No2 People address ex: Pico Rivera, California

1: At least one of the 3 options should not be empty
2: the 3 options should be present if one at least is used

Example input data

1,736233,1,,
2,730247,,,
3,640139,,2,
4,726263,7,,
5,726579,9,,
6,725038,11,,
7,13249,,20,
8,781163,,,ceo
9,1442719,,,managing director
10,24870,,,csm's

Responses

Here are the major responses the API may return.

for details on the errors, please refer to the API Error Codes article.

HTTP 200

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

application/json example response

{
  jobId: "peerukbkasr85s6hdtb9"
  status: "accepted"
  type: "targetLookup"
}

application/json example response

<?xml version="1.0" encoding="UTF-8"?>
<BulkJobStatus>
 <jobId>a8bpdds1one7vblg0obm</jobId>
 <status>accepted</status>
 <type>peopletab</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.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk