Salesforce Spring’14 Data.com Search API and Data.com Match API

Share on facebook
Share on twitter
Share on linkedin
In spring 14 release, Data.com Search API and Data.com Match API extend the current capabilities currently of Data.com Prospector and Data.com Clean.

In spring 14 release, Data.com Search API and Data.com Match API extend the current capabilities currently of Data.com Prospector and Data.com Clean.

data.PNG

Data.com Search API:
The Data.com Search API works with DatacloudCompany, DatacloudContact, DatacloudDandBCompany, DatacloudSocialHandle objects. These objects are Datacloud objects. Using Data.com Search API, searches are made possible in the SOQL based interface that searches the database for contacts and companies, and returns information based on the search criteria.

Data.com Search API is available in following Salesforce editions,
➔ Developer Edition
➔ Professional Edition **
➔ Enterprise Edition
➔ Performance Edition

** Available via add-ons

Limitations:
1,000 daily calls for every Data.com Prospector license purchased in an organization. This limitation is bound to 24-hour rolling period of time. To increase number of daily calls, purchase more Prospector licenses. For example, if you purchase 5 prospector licenses, you will get 5 x 1000 calls limit for a day in an organization.

Request and Response:
Salesforce Object Query Language is used to build powerful queries to access records from Data.com for Contact and Company objects.

Example:
SELECT ContactId, LastName, FirstName, State
FROM DatacloudContact
WHERE State = ‘TN’
ORDER BY LastName
LIMIT 15
This API supports only one fieldExpression clause for ORDER BY. Entering more than one fieldExpression clause will cause error.

Data.com Match API:
Let’s find the difference between records that are stored in Datacloud objects–Contact and Company. This API finds matching records and identifies which fields are different from your query.

The REST API for Data.com Match has two resources.

  • DatacloudContact: Returns matched data from Contacts in the Data.com database.
  • DatacloudCompany: Returns matched data from Companies in the Data.com database.

Use POST requests to match your data with records in Data.com.Match API and Search API share the same call limitations.The Match API is available to customers who have purchased Data.com Full Clean.

The following URI are the REST URI for DatacloudContact and DatacloudCompany: https://na1.salesforce.com/services/data/v30.0/match/DatacloudMatchEngine/DatacloudContact/ https://na1.salesforce.com/services/data/v30.0/match/DatacloudMatchEngine/DatacloudCompany/

❖ instance (https://na1.salesforce.com)
❖ version information (/services/data/v30.0)
❖ resource (/match/DatacloudMatchEngine/DatacloudCompany)

Request:
The sample XML request is as follows,
<fields>City</fields>
<fields>CompanyId</fields>
<fields>CompanyName</fields>
<fields>ContactId</fields>
<fields>Country</fields>
<fields>Email</fields>
<fields>FirstName</fields>
<fields>IsInactive</fields>
<fields>LastName</fields>
<fields>Phone</fields>
<fields>State</fields>
<fields>Street</fields>
<fields>Title</fields>
<fields>Zip</fields>

Response:
The response of the API contains three parts, they are

  • errorCode – There is specific code for each and every errors. The errormessage will contains other details.
  • entities – Entities contain attributes, and each attribute contains elements. The elements contain fields.
  • matchDiffs – It contains the matched record and field value mismatches.

About MST

At MST Solutions our cornerstone is to adapt, engage and create solutions which guarantee the success of our clients. The talent of our team and experiences in varied business verticals gives us an advantage over other competitors.

Recent Articles

Require Permission to View Lookup Fields (Critical Update)

We have a scenario to assign the record owner to a Queue based on some criteria. The non-admin users are unable to view the value of the Owner field once the Owner field is updated with the Queue. We found the root cause for this issue. One of the features of the Spring 20 release (Require Permission to View Record Names in Lookup Fields (Critical Update) causes this issue.

Read Article »

Work with us.

Our people aren’t just employees, they are key to the success of our business. We recognize the strengths of each individual and allow them time and resources to further develop those skills, crafting a culture of leaders who are passionate about where they are going within our organization.